Gated pipelines provide control for administrators and release managers on when a given software release is deployed to a tightly protected environment (e.g. production).
The execution of jobs that perform certain tasks (e.g. deployment) targeting the downstream environment beyond the "gate" step is done only upon either an approval coming from an external Change Control system or an explicit manual trigger of such step.
Here are a few samples of this pattern:
