The Execute All step is a hybrid step that 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.
| Info |
|---|
If a utility project that is to be executed does not have a mapped target that is associated with the pipeline stage's environment, the execution of the project will be skipped. |
...
Field | Description |
|---|---|
Name | The name of the step. |
Description | An optional description for the step. |
Include Groups | Identifies which group or groups from the snapshot to deploy/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 deploying/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. |
Force Execute | 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 and methods while using the Groovy Editor. The script must return true if the gate 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 |
...