Comparison
Deployment gatevsPost-deploy verification
Deployment gate
the pipeline stops and waits for a human to press a button, or for a metric to stay inside a threshold for ten minutes.
A condition that must be satisfied before a pipeline proceeds — a human approval, a test result, an automated check on live signals. Automated gates are the useful kind, since they encode a specific belief about what makes a release safe. Manual gates mostly measure how quickly someone reads Slack, and they degrade into rubber stamps precisely when they are needed most.
Full entry →Post-deploy verification
the pipeline hits three real endpoints after the rollout and fails the deploy if any of them is unhappy.
Automated checks run against the deployed system immediately after a release, distinct from the tests that ran against the artefact. They catch the class of failure that only exists in the real environment: missing configuration, absent permissions, an unreachable dependency. They are the precondition for automated rollback, because something has to decide the deploy failed.
Full entry →