Available Stage Options
Skip looking into rule from source control by standard within the agent directive. For instance: choices
Set a timeout duration with this phase, after which it Jenkins should abort the phase. For instance: choices
This stage the specified number of times on failure, retry. For instance: options
Prepend all system production generated in this phase with all the right time of which the line ended up being emitted. As an example: choices
The parameters directive provides a summary of parameters that a person should offer whenever triggering the Pipeline. The values for those user-specified parameters are distributed around Pipeline actions through the params object, begin to see the Parameters, Declarative Pipeline for the certain use.
Only one time, within the pipeline block.
A parameter of the sequence kind, as an example: parameters
A text parameter, that could contain lines that are multiple as an example: parameters
A boolean parameter, as an example: parameters
A selection parameter, for instance: parameters
A password parameter, as an example: parameters
A list that is comprehensive of parameters is pending the conclusion of INFRA-1503.
The causes defines that are directive automated ways that the Pipeline should be re-triggered. For Pipelines that are incorporated with a supply such as for instance GitHub or BitBucket, triggers may possibly not be necessary as webhooks-based integration will most likely currently be there. The causes now available are cron , pollSCM and upstream .
Just once, within the pipeline block.
Accepts a string that is cron-style define a consistent period of which the Pipeline must be re-triggered.
Accepts a cron-style sequence to define a frequent period at which Jenkins should search for brand brand brand new supply modifications. If brand brand new modifications occur, the Pipeline will undoubtedly be re-triggered.
Accepts a comma-separated sequence of jobs and a limit.