Versions Compared

Key

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

The Wait step will halt the pipeline stage execution for a set amount of time (seconds), until a specified date and time is reached, or an override role member skips the wait period.

...

Field

Description

Name

The name of the step.

Description

An optional description for the step.

Wait (Seconds)

Number of seconds to halt the pipeline stage execution.  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).

Wait Till

Halt the pipeline stage execution until the given date and time is reached.  Either Wait (Seconds) or Wail

TIll

Till is required.

Schedule Override Role

The pipeline role that has privileges to override the step if required.  If not specified, only a FlexDeploy Administrator can override the step. 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 return [type: 'groupName', value: 'FD Administrators']. Supported types are roleId, roleName, groupId, and groupName. You can return Map with single key/value pair or list of such single key/value maps.

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 return [type: 'groupName', value: 'FD Administrators']. Supported types are roleId, roleName, groupId, and groupName. You can return Map with single key/value pair or list of such single key/value maps.

Info

Either Wait Duration or Wail TIllTill is required.

Script Variables

...