1.

Figure 1
Approve the request now

2. Go ahead and load the production site using the “FF PROD” favorite in Internet Explorer. You
may need to refresh the page a few times before the build is fully deployed (displaying “Support
v2.0”).

Figure 2
Deployment to the production environment is a success

3. The Ops Team now needs to validate the deployment. Select the request and then select the
Approve button.

Figure 3
Approving the deployment to production
 4. In the Successful Deployment Confirmation window, enter a comment such as “Ops approved”
and then select the OK button. The operations team may have their own suite of tests that they
run to ensure that everything is running as expected and ready for end-users.

Figure 4
Approve the deployment to production

5. Navigate to Releases | Releases and note that the release has made it to the target stage of
“Prod” and has a Status of “Released”.

Figure 5
Build has been released to production

Task 5: Initiating a Manual Release

1. There are circumstances where being able to manually trigger the release of a specific build
using the same process would be useful. For example, let’s say that it has been discovered that
the production site has some scaling issues (that unfortunately weren’t discovered before the
previous release made it to production), and we would like the QA team to do some
comparative testing using their toolset against the QA environment.
2. Select the Configure Apps | Agent-based Release Templates tab, select the Fabrikam Call
Center template, and then click the New Release button.
3.