Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

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 on the projects in the release.  If no group is specified, all projects (excluding utility projects) in the release will be deployed.

Force DeployWhether 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.
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 drop-down.  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).

ContinueIf 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 failure.

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.

  • No labels