Execute All Step
- Erick Jones
- Jay-Ar Brouillard
- Ben Hoffman
The Execute All step is a hybrid which performs the function of both the Deploy All and Execute All Utility steps. Â That is, it deploys all project versions in the snapshot and executes all utility projects defined in the release, taking into account the priority defined on the release.
If a utility project that is to be executed does not have a mapped instance that is associated with the pipeline stage's environment, the execution of the project will be skipped.
Field | Description |
|---|---|
Step Name | The name of the step. |
Description | An optional description for the step. |
Project Groups | Identifies which group or groups from the snapshot to deploy.  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 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. |
Project Groups | Identifies which group or groups (coma separated) from the snapshot to deploy (or from the release to execute for Utility projects). Â The group name(s) must match those defined on the projects in the release. Â If no group is specified, all projects in the release will be deployed/executed. |
Force Deploy | Whether or not to force deploy the projects. Â If true, this is equivalent to checking force deploy when individually deploying a project to an environment through the deploy request form. Â 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). This field is not applicable to Utility projects. |
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 methods using Variable Lookup help. 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). |
Continue | If checked, any failure will be ignored, and the pipeline execution will continue. |
Notify Pipeline Roles | Optionally 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. |
The Execute All step uses the priority for each project/package contained within the release. Â If a deployment fails, projects or packages 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