The Deploy All step deploys all project versions (or packages) in the snapshot, 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) from the snapshot to deploy. The group name(s) must match those defined project groups are defined by the pipeline, and tagged on the projects/packages in the release. If no group is specified, all projects (excluding utility projects) in the release will be deployed |
| 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. |
| 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). |
| 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 Deploy 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. |
...