Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Utility step executes a named utility project in the release.

Info

If the utility project being deployed executed does not have a mapped instance for 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 Name

The name of the utility project in the release to execute.  This project must be in the release, or the execution will fail.

FlexFieldsIf Deploy Request FlexFields are configured, entry will be prompted for on the step configuration (not shown above).  If the information is provided in the stage execution info, it will override the data entered on the step configuration.
InputsIf the utility workflow for the project has inputs, entry will be prompted for on the step configuration (not shown above).  If the information is provided in the stage execution info, it will override the data entered on the step configuration.
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).

ContinueIf checked, any failure will be ignored, and the pipeline execution will continue.
Notify Pipeline RolesSelects 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.

...