Any or folder can be bound to a configuration management instance for approval. This configuration is used for linking/creating CMS tickets during ad-hoc deployments, and can bind an approval to the linked ticket. Additionally, pipelines can be designed with External Approval Gates to create and/or link CMS tickets and bind the gate approval for the stage or project to the status of the underlying ticket.
| Table of Contents | ||||
|---|---|---|---|---|
|
Folder
The Approval tab allows association of approvals in an environment with any Change Management Instance configured in the topology. Open a folder and locate its Approvals tab. Folders inherit their Approval settings from their parent folders. You can override it at any level, either in the root FlexDeploy folder, or any of its children. Approvals added here will cascade down to child folders and projects and apply to all manual deployments. Deployment through a release will not be affected by these approvals.
...
Any inputs needed to create a ticket are locked in Groovy mode. This means that you can type code in the box. Pressing Ctrl+Space will auto complete what you are typing. See Working with Groovy for more information.
See https://flexagon.atlassian.net/wiki/spaces/FD60/pages/9856632350/Change+Management+Systems#Ticket-Fields for information about what the specific fields require.
Release/Pipeline
Similar configuration can be defined for External Approval Gates within a pipeline. When using pipelines, the CMS configuration defined on folders is ignored, since the configuration from the External Approval Gates themselves is used . See Creating/Editing a Pipeline Version for details regarding the External Approval Gate.Details of specific Ticket Fields are available on individual change management systems page.
| Child pages (Children Display) | ||
|---|---|---|
|