The Schedule step blocks until the current date/time evaluates to the given cron expression, or the configured FlexDeploy group pipeline role overrides to continue.
...
For details on Cron Expression Syntax see
...
Field | Description |
---|
Name | The name of the gate. |
Description | An optional description for the step. |
Schedule Cron Expression | The |
Cron Expression to use for setting up the schedule. Sample cron expressions are provided in the |
drop-down. |
Cron Expressions entered are descriptively parsed if valid.
|
|
This allows for Cron Expressions that are scheduled to run on the 2nd and 4th Friday which is not normally possible with Quartz Cron.
| |
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). | |
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 is applicable, or false otherwise. If no script is provided, the default is to return true (applicable). | |
Continue | If checked, any failure will be ignored, and the pipeline execution will continue. |
Notify Pipeline Role |
SSelects 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). |
Script Variables
Include Page | ||||
---|---|---|---|---|
|
...