User guide

26
Note: When debugging to find the reason why a deployment failed, it can be helpful to execute the
installation command (which can be found in the Log) manually in a command prompt on the targeted
server.
12. Choose the Retry Failed Deployment button in the Release form title bar.
13. Go back to the Log tab and verify that the deployment was successful.
2.12.5 Validate Deployment
We are assuming that the release has been deployed successfully into the current stage environment.
14. If you are the owner (Approver) of the Validate Deployment step, go to the Action Requests tab. The
action requests table will contain a Validate Deployment action request.
15. Once you have completed the deployment of the component, select the Validate Deployment action from
the list and choose the Approve button on top of the action request list.
2.12.6 Approve Release
We are assuming in this section that the Approve Release step status is Pending and that the release
path for the current stage have approvers defined.
16. If you are the owner (Approver) of the Approve Release step, go to the Action Requests tab. The action
requests list should contain an Approve Release action request.
17. Select the Approve Release action from the list and choose the Approve button on top of the action
request list.
Note: The release will not move to the next stage until all approvers have approved the release.
2.13 Trigger a Release from Team Build
The current support for triggering releases from Team Build is done using a custom Build Process
Template.
2.13.1 Pre-requisites
To be able to start a Release from a build, a release management Client needs to be installed on the machine(s)
running the TFS build agent. Configure the Client to point to the release management Server. In order to trigger a
release from a build, the release template must first be configured correctly. From the release template detail view
select “Can Trigger a Release from a Build?” found under the Properties editor.
By selecting this flag we are telling release management to accept requests from a Team Foundation Build to start a
release. If this flag is not set, the request coming from a Team Foundation Build will simply be ignored and the build
will fail.
Restrictions
Only release templates for which all its components have been configured to “Builds with application” or “Builds
externally” will be deployed in this way. In other words, if a release template is using a component that “Builds
Independently” it cannot be deployed automatically from a build.
The Acceptance Step and the Deployment Step of the first stage of the associated release path must be set to
Automated.