Implementing pipeline gates
Gates ensure that orchestrations cannot be started in an environment until the gate rule is satisfied.
About this task
A gate is a condition that determines whether an applications can run in the environment. A
pipeline can have some environments with gates and some without gates. A gate
condition is called a rule. You can define a rule type based on the following criteria:
- Manual requires one or more responders to approve an
application version before it can run in an environment. Approving a gate
rule is considered passing the gate.Note: Anyone with access to the pipeline can create gates and be assigned as a responder. Scenarios detailing approval and rejection of application versions by responders are detailed below.
- If a gate has multiple responders, one approval is sufficient for the application version to pass the gate.
- If one responder rejects the application version, the application is rejected.
- If responders both approve and reject the application version, the application is rejected.
- When you add gates to an environment, all application versions in the affected environment must be approved before a deployment can be started. You can override a failed gate, that is, a rejected application version and you may want to do this when you run applications in a test environment.
- Automated leverages a metric-based system allowing
you to automatically stop or advance application versions from being
deployed into environments based on set conditions for the rule.Note: Using the automated rule type will provide you with visibility on the movement status of application versions and automated governance across your pipeline.
To add a gate to an environment, complete the following steps:
Procedure
For the environment where you want to add a gate, click
and select Add
gate, and then complete the following steps.

Note: For the environment where you want to modify a gate, click
and select Edit
gate, and then complete the following steps.
