Jobs that run after a deploy

This is a question about style, rather than how to make stuff work, but I’m curious about how other people deal with this.

Say I have a deploy job like this:

deploy:
    ...
    environment:
        name: production

And then a job that runs after it:

stages:
    ...
    - deploy
    - verify

...

verify:
    environment:
        name: production

Is it common to use action: prepare on the environment for the verify job?

Without action: prepare integrations like Slack notifications will send duplicate messages saying “about to deploy…”, but prepare seems wrongly named to me, because it’s useful both before and after the deployment has completed.

3 Likes