Execute All Utility Step
The Execute All Utility step executes all utility projects in the release, taking into account the priority (configured on the release content).
Field | Description |
---|---|
Name | The name of the step. |
Description | An optional description for the step. |
Include Groups | Identifies which project group(s) from the snapshot to execute.  The project groups are defined by the pipeline, and tagged on the projects/packages in the release. If no groups are specified, all projects/packages from the snapshot will be included. |
Exclude Groups | Skip executing any projects/packages from the snapshot which are tagged in the release with the selected project group(s). Available project groups are defined by the pipeline. |
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 step is applicable, or false otherwise. Â If no script is provided, the default is to return true (applicable). |
On Error | |
Continue | If checked, any failure will be ignored, and the pipeline execution will continue. |
Notify Pipeline Roles | Selects one or more roles from the pipeline definition to notify in case of error. Default role members are defined on the pipeline, and optionally overridden for each release. 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 |
The Execute All Utility step uses the priority for each utility project configured in the release. Â If an execution fails, projects with a higher priority will not be submitted, and the step will fail.Â
If the projects have FlexFields or Inputs defined, values must be provide on the stage execution info screen. Â If the values are required and not specified, the underlying workflow execution will fail.
Script Variables
- style