The Approval gate creates Task(s) for member group(s) of configured Approval Role, and blocks until one of the Task is either approved or rejected (either through the release dashboard or the approval tasks page or via Emails). If there are no member groups for Approval Role, then Task is created for any Administrator group.
...
When approval gate is executed, email will be sent to members of Approval Role.
Individual email is sent for
One email for each Each group member of Approval Role. i.e. if there are two groups in Approval Role, two individual emails will be sent for each group’s users.
All user members of Approval Role
All email addresses member of Approval Role
...
Field | Description |
|---|---|
Name | The name of the gate. |
Description | An optional description for the gate. |
Approval Role | The pipeline role which is responsible for approving or rejecting the task associated with this gate. Optionally, use a Groovy expression to make this field dynamic based on some contextual value (e.g. a property defined on the pipeline, and specified on the release). When using a role script you can dynamically return a key/value pair. For example If not specified, only a FlexDeploy Administrator can approve or reject the gate. |
Precondition | An optional Groovy script which determines whether the gate or step is applicable during execution. The script has access to variables and methods listed in Pipeline Groovy Variables and Methods. You can find these variables and methods while using the Groovy Editor. The script must return true if the gate is applicable, or false otherwise. If no script is provided, the default is to return true (applicable). |
...