The input directive on a phase permits you to prompt for input, utilising the input action. The phase will pause after any choices have now been used, and before going into the representative block for that phase or assessing the whenever condition of this phase . Then continue if the input is approved, the stage will. Any parameters supplied within the input distribution will be accessible into the environment for the remainder phase .
Needed. This is presented to your user once they head to submit the input .
An optional identifier for this input . Defaults to the level title.
Optional text for the «ok» switch from the input kind.
An optional comma-separated a number of users or group that is external that are permitted to submit this input . Defaults to enabling any individual.
An optional name of a breeding ground adjustable to create with all the submitter title, if current.
An list that is optional of to prompt the submitter to offer. See parameters to find out more.
The whenever directive allows the Pipeline to see whether the phase ought to be performed according to the offered condition. The whenever directive must include a minumum of one condition. In the event that when directive contains one or more condition, all of the kid conditions must return real for the phase to perform. Here is the just like if the son or daughter conditions had been nested within an condition that is allOfstart to see the examples below). If an anyof condition is utilized, remember that the disorder skips staying tests the moment the very first «true» condition is available.
More technical conditional structures can be built with the nesting conditions: maybe maybe not , allOf , or anyOf . Nesting conditions might be nested to virtually any arbitrary level.
In the stage directive
Execute the phase as soon as the branch being built matches the branch pattern (ANT design course glob) offered. Observe that this just works on a multibranch pipeline.
The parameter that is optional can be added after an characteristic to specify exactly just how any habits are examined for the match: EQUALS for a straightforward string contrast, GLOB (the standard) for the ANT design course glob (identical to for instance changeset ), or REGEXP for regular phrase matching. For instance: whenever
Execute the phase whenever a tag is being built by the build. Example: when
Execute the phase in the event that buildвЂ™s SCM changelog contains an offered expression that is regular, for instance: whenever
Execute the phase in the event that buildвЂ™s SCM changeset contains more than one files matching the offered pattern.
The parameter that is optional could be added after a characteristic to specify exactly just how any habits are assessed for the match: EQUALS for a straightforward sequence contrast, GLOB (the standard) for an ANT design course glob case insensitive, this could be switched off aided by the caseSensitive parameter, or REGEXP for regular phrase matching.
Executes the phase in the event that build that is current for a «change request» (a.k.a. Pull Request on GitHub and Bitbucket, Merge Request on GitLab, improvement in Gerrit, etc.). Whenever no parameters are passed away the phase operates on every modification demand.
The stage can be made to run only on matching change requests by adding a filter attribute with parameter to the change request. Feasible characteristics are id , target , branch , fork , url , name , writer , authorDisplayName , and authorEmail . All these corresponds up to an environment that is change.
The optional parameter comparator could be added after a feature to specify exactly exactly just just how any habits are assessed for the match: EQUALS for an easy sequence contrast (the standard), GLOB for the ANT design course glob (identical to for instance changeset ), or REGEXP for regular phrase matching. Example: when
Execute the phase if the specified environment variable is scheduled towards the provided value, for instance: whenever
Execute the phase whenever anticipated value is add up to the value that is actual for instance: whenever
Execute the phase as soon as the specified Groovy phrase evaluates to real. Observe that when strings that are returning your expressions they need to be transformed into booleans or get back null to gauge to false. Merely returning «0» or «false» will nevertheless assess to «true».
Execute the phase if the TAG_NAME variable matches the offered pattern. Example: when. If a pattern that is empty supplied the phase will perform if the TAG_NAME adjustable exists (same as buildingTag() ).
The optional parameter comparator could be added after a feature to specify just exactly how any habits are examined for the match: EQUALS for an easy sequence contrast, GLOB (the standard) for the ANT design course glob (just https://www.title-max.com/title-loans-ct/ like for instance changeset ), or REGEXP for regular phrase matching. For instance: whenever
Execute the phase if the nested condition is false. Must include one condition.
Execute the phase whenever all the nested conditions are real. Must include one or more condition. For instance: whenever allOf branch ‘master’; environment name: ‘DEPLOY_TO’, value: ‘production’
Execute the phase whenever a minumum of one of the nested conditions does work. Must contain one or more condition. As an example: whenever anyOf branch ‘master’; branch ‘staging’
Execute the phase as soon as the present create has been brought about by the param provided. For instance:
Assessing whenever before entering representative in a phase
By default, the when condition for the phase will be assessed after going into the representative for the phase , if a person is defined. Nonetheless, this is changed by indicating the beforeAgent option in the anytime block. If beforeAgent is placed to true , the whenever condition will first be evaluated, in addition to representative will simply be entered in the event that whenever condition evaluates to real.