The Promote to Release step promotes the current snapshot project/package versions to specified release. If project/package are not part of target release, then they are added as part of this step execution. 
. If a project/package is added to the target release, then the deploy priority and project groups from the source release for that project/package will be assigned. A project group will only get copied if there is a project group with the same name (case sensitive) that exists on the target release. If a project group with the same name (case sensitive) is not present on the target release, then it will be ignored. Lastly, if the project/package already exists in the target release then the deploy priority and project groups will not be updated.
Field | Description | ||
|---|---|---|---|
Name | The name of the step. | ||
Description | An optional description for the step. | ||
Project | The name of the utility project in the release to execute. This project must be in the release, or the execution will fail. | ||
Promote to Release | The target release where current snapshot should be promoted. 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 script you can dynamically return Release Name as String value. If release configured is not valid or is not STARTED then this step will fail. If project/packages in current snapshot are not part of target release content, then they will be added automatically on target release content. Standalone Releases can not be used as Promote to Release, rather standalone release may be suitable for promote to other releases. | ||
Promoted Snapshot Description | Optional description of the new snapshot on the target Release after promotion. | ||
Snapshot Inputs | Release Snapshot Inputs on the chosen target 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 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 Roles | 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
| Include Page | ||||
|---|---|---|---|---|
|