1.

automatically installed to the deployment environment, and finally validated by Brian once
again.

Figure 1
“Prod” stage historical workflow

2. Select the Previous Stage link.

Figure 2
Location of Previous Stage link
3. This stage was setup to be for QA. Note that this stage has more workflow automation in place
– it automatically accepts, installs, and validates the application and then waits for a QA team
member to approve it.

Figure 3
“QA” stage historical workflow

Note: The setup used for the stages seen in this lab are for demonstration purposes only. In
normal scenarios, the QA stage would not automate the acceptance step. It would usually be
setup for an owner of that stage to decide when to deploy a new version.

4. Select the Previous Stage link to view the “Dev” (development) stage history. There is quite a
bit of automation going on here as well, but note that manual approval was necessary in order
for transition to the QA stage. This final approver simply indicates that the current version
meets all needed quality gates and should be made available to the next stage (QA in this case).
We will see how all of this is configured later on in this lab, but for now just remember that the
flow through the different stages (Dev -> QA -> Prod) is what we refer to as the release path.