Lesson 2: Adding an approval to the release
You can add approval requests to the phases in a release. When you add an approval request, the approval must be provided before deployments that are scheduled for that phase can start.
In this lesson, you use the Release Detail page to add an approval request to the DEV phase of the release you created in the previous lesson. Later in the tutorial, when you run a deployment for the DEV phase, you must approve the request before the deployment can start.
From the Release Detail page for the Demo Release, click the
Edit Phase icon for the DEV phase, as shown in the following figure:
The Phase Approvals area is displayed, as shown in the following figure:
Unless you copy a release, new releases use the Default Plan deployment plan for each phase in the release. If you schedule a deployment by using the Pipeline view, the plan in the Default Plan field is used. Each phase can have its own default deployment plan assigned to it. If you schedule a deployment by using the Deployments page, you can select any deployment plan associated with the release. You are not constrained to use the deployment plan in the Default Plan field. In this tutorial, you add tasks to the Default Plan, so you do not need to change it.
- In the Phase Approvals area, click Add New.
In the Approval dialog box, in the Approval Name
In the Role list, select Release Manager.
A user with the Release Manager role must approve any deployment that is scheduled for the DEV phase, including the deployment that you run in a later lesson.
The approval request is listed in the Phase Approvals area.
In this lesson, you added an approval request to the release's DEV phase. Any deployment that is scheduled for the DEV phase must be approved by a team member in the selected role.
To learn more about approvals, see Creating releases and specifying release details.