Page Comparison

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

Step

Name	The name of the gate.
Description	An optional description for the step.
Schedule Cron Expression	The

FlexDeploy group which is responsible for approving or rejecting the task associated with this step

Cron Expression to use for setting up the schedule. Sample cron expressions are provided in the

Image Removed drop

drop-down.

A free cron expression builder such as Cron Maker can also be used, but it must be compatible with

http://www.quartz-scheduler.org/documentation/quartz-2.2.2/tutorials/crontrigger.html#crontrigger-tutorial.

TipStarting in the 4.6 release, multiple

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).

Tip
Multiple Cron Expressions can be specified using semicolon as a

delimeterA new Admin Screen was added to test expressions in the Administration Menu on the Admin Operations Screen.

delimiter. For example,

0 0 11 ? * *;0 0 12 ? * *

is equivalent to

0 0 11-12 ? * *

This allows for Cron Expressions that are scheduled to run on the 2nd and 4th Friday which is not normally possible with Quartz Cron.

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

which is allowed to continue execution prior to the step completing on the configured schedule

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

using Variable Lookup help

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 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

optional

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.

Script Variables

Include Page

	FD70:Pipeline Groovy Variables and MethodsFD70:
	Pipeline Groovy Variables and Methods

...

Versions Compared

Old Version 1

New Version Current

Key

Script Variables