Stage Execution Information is the mechanism to provide input to the stage steps or gates. Such information is required for:
You can enter the stage execution information on the dashboard after the stage execution has been initiated by clicking on the paper-clip
icon in the stage header.
Enter the desired values for related change ticket(s), inputs, and Flexfields for each project that needs them, or use the Clipboard icon to copy the value up and down the column.
If you make large use of inputs/flexfields for your projects, you may upload a CSV file containing the values. You can also download a sample CVS file which may be used as a template to create the file.
The related ticket can be set at the stage level or for individual projects/packages in the snapshot. If the ticket is set at the stage level all workflow requests in the stage will be associated with the same ticket. All related tickets must be approved prior to passing through an external approval gate.
The related ticket fields become read-only after an external approval gate is cleared.
The Deployment Overrides column provide a way to force or skip a project or package during any stage execution. This can be set manually opening this screen if there is a failure for one of the package and if you want to skip that package and continue with other line items in the release. You can also use the Custom Gate or Custom Step to set the override option using the API methods to set the values dynamically for each execution. No Override just reset any option selected as well as uses the default behavior of the deployment execution. This option is available from FlexDeploy 188.8.131.52.
While FlexFields and workflow inputs provide a mechanism to make late binding decisions at runtime, they can also be an inhibitor to fast and iterative software delivery since there is a dependency on manual data entry with each and every execution. From FlexDeploy 184.108.40.206, you can set the FlexFields and Workflow inputs using Custom Gate and Custom Step. API methods are available to set the values dynamically for each execution. You will want to take that into consideration during your process design.
The snapshot variables tab lists the current value of any snapshot variables used within the pipeline. If the snapshot variable has not been set by a custom gate or step the variable will be listed but the value will be empty.
Note that the values displayed are always the value at the current time and do not represent the value during execution of the particular stage. The values will match across all stages at any given time, and viewing it within a specific stage is for convenience only.