Schedule Step
The Schedule step blocks until the current date/time evaluates to the given cron expression, or the configured pipeline role overrides to continue.
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. 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). Multiple Cron Expressions can be specified using semicolon as a delimiter. For example, 0 0 11 ? * *;0 0 12 ? * * is equivalent to 0 0 11-12 ? * * For details on Cron Expression Syntax see http://www.quartz-scheduler.org/documentation/quartz-2.2.2/tutorials/crontrigger.html#crontrigger-tutorial |
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 |
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 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 Role | 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 |
Script Variables
- style