During the exploratory stage, various stakeholders may be required to run through some verification before promoting to the next stage. Using a self-service deployment based on the image generated during the Acceptance Stage, each required stakeholder can verify system behavior. Once completed, each stakeholder will go to the CI system and click a button to approve promotion to the next stage. Once all approvals are submitted, the pipeline automatically goes to the next stage.
After the software system release candidate gets to the exploratory stage, it will automatically send an email to the address that you configured in lesson 1. It will look something like what you see here.
Then, you will follow the instructions which indicate that you will run a self-service deployment to launch your own environment.
In the third and final step of the exploratory stage, you will go to the job described in your email instructions, enter the pipeline id and select Accept or Reject. If you accept it, it continues down the production line; if you reject it, it stops the line and an email error is sent to the team.
So, by using this process of receiving an email, launching an environment based on the specific commit, running through manual verification and then approving or rejecting the release candidate, you can incorporate manual actions into a fully-automated deployment production line.