The Execute All Utility step executes all utility projects in the release, taking into account the priority (set on the release projects).
Field | Description | ||
|---|---|---|---|
Step Name | The name of the step. | ||
Description | An optional description for the step. | ||
| Project Groups | Identifies which group or groups | (coma separated) of utility projects in the release to execute. The group name(s) must match those defined on the projectsfrom the snapshot to deploy. The project groups are defined by the pipeline, and tagged on the projects/packages in the release. | If no group(s) is specified, all utility projects in the release will be executed (according to priority)If no groups are specified, all projects/packages from the snapshot will be included. |
| Exclude Project Groups | Skip deploying 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 the expression | ||
| Continue | If checked, any failure will be ignored, and the pipeline execution will continue. | ||
| Notify Release ManagersIf checked, an email notification will be sent to the release managers (configured on the release) on failurePipeline 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 optional overridden for each release. |
| Tip |
|---|
The Execute All Utility step uses the priority for each project/package contained within 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. |
...