August 2017
Intermediate to advanced
332 pages
9h 16m
English
In general, the Continuous Delivery pipelines should be fully automated, triggered by a commit to the repository, and end up after the release. Sometimes, however, we can't avoid having manual steps. The most common example is the release approval, which means that the process is fully automated, but there is a manual step to approve the new release. Another common example is manual tests. Some of them may exist because we operate on the legacy system; some others may occur when a test simply cannot be automated. No matter what the reason is, sometimes there is no choice but to add a manual step.
Jenkins syntax offers a keyword input for manual steps:
stage("Release approval") { steps { input "Do you approve the release?" ...Read now
Unlock full access