The External Approval gate blocks stage execution until the attached change ticket is approved or rejected. Change tickets can also be automatically created by External Gate if Create Ticket is checked. Change Ticket can be defined per Project/Package combination or single for all Project/Packages in Snapshot. User must enter Change Ticket as necessary on Stage Execution Information if Create Ticket is not checked. Change Ticket can also be set using Custom Gate if necessary.
...
Field | Description |
|---|---|
Name | The name of the gate. |
Description | An optional description for the gate. |
Approval Role | The pipeline role which is allowed to approve or reject the gate in FlexDeploy outside of the Chanage Management System. Provides mitigation in event that CMS is unavailable for any reason. Approval tasks are created for the group members of this role, and will be automatically approved or rejected based on the status of the associated ticket. If no group member is assigned to the role, the task is assigned to a group designated as a FlexDeploy Administrator. 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). |
CMS Instance | The Change Management System instance to use for this external gate. |
Create Ticket | Determines whether to automatically create a CMS ticket when this gate is reached. If unchecked, it is expected that the related ticket field for either the stage or the individual projects/packages is populated (either manually by the user or through a Custom Gate). |
Precondition | An optional Groovy script that 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). |
Scope | Only applies when Create Ticket is checked. Determines the scope for setting the created ticket number. If scope is Stage, the related ticket field of the stage is updated to the created ticket number. If scope is Project/Package, a ticket will be created or each project/package in the snapshot and the corresponding related ticket field is updated. |
<Ticket Fields> | Only applies when Create Ticket is checked. Used to set the values of individual ticket fields when creating a ticket. By default, the ticket field mapping comes from the global configuration. Use a Groovy expression to the values for the individual ticket fields and make them dynamic based on some contextual value (e.g. a property defined on the pipeline, and specified on the release). |
...