Manual Step
- Karl Henselin
- Rajashekar.Gaddi
The Manual step creates a task for the assigned group, and blocks until the task is either approved or rejected (either through the release dashboard or via the REST API, or via Emails(pipeline groups and users can complete the task)).  This is useful when there are manual steps which must be performed in between automated steps executing within a stage.
Field | Description |
|---|---|
Step Name | The name of the step. |
Description | An optional description for the step. |
Assigned Role | The pipeline role which is assigned to this manual step. |
Estimated Duration | Estimated time (in minutes) to complete the task. Â Informational only. |
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 methods using Variable Lookup help. 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 optional overridden for each release. |
Completing manual steps via the REST API is not supported at this time.
Script Variables
- style