The Manualstep creates a task for the assigned group, role and blocks the stage execution until the task is either approved or rejected (either through the release dashboard, or via the REST API, or via Emails(pipeline groups roles and users can complete the task)). This is useful when there are manual steps which that must be performed in between automated steps executing within a stage.
...
Field | Description |
|---|
Name | The name of the step. |
Description | An optional description for the step. |
Approval Role | The pipeline role which is assigned to this manual step. |
Estimated Duration
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). | |
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 gate is applicable, or false otherwise. If no script is provided, the default is to return true (applicable). | |
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). |
Script Variables
| Include Page | ||||
|---|---|---|---|---|
|