Release your app to environments with deployment agents

Last Update: 4/7/2017

Visual Studio 2015 | Team Services | TFS 2015 | Previous version

horizontal-line

information A newer version of Release Management is available

Release Management features have been integrated into the Build & Release hub in Team Foundation Server (TFS) and Visual Studio Team Services. For more information, see Continuous integration on any platform.

The newer web-based version is the recommended alternative to the server and client version described in this topic. If you do not already have Release Management installed, we encourage you to use the web-based version in TFS 2015 Update 2 and above or Visual Studio Team Services instead of the version described here. If you are already using an earlier server and client version, you should be aware that no new features will be added to these versions.

horizontal-line

If you want to use PowerShell, DSC or Chef to deploy your app, you must use vNext environments; go here for instructions. Otherwise if you are using deployment agents, follow these steps.

If you haven't already done so, connect to release management and add stages for your release.

Set up servers and environments

  1. Install and configure a deployment agent on any machine that will be part of the environment used to deploy your app.

  2. Scan for new servers that already have deployment agents installed. If the server you want to use is not in the list, check that the service for the deployment agent (Microsoft Deployment Agent) is started on that machine.

    Scan for servers

  3. Register the servers to use for your environments. You will deploy your app to the servers in an environment as part of your release process.

    Register your server to use in the release process

  4. Create environments for each of your stages. Link the servers to your environments.

    Add an environment

    An environment can contain multiple servers.

Create a release template

Check the code for your app has been added to version control. You also need a build definition that builds your app.

  1. Create a release path to represent the stages that your release must go through.

    Create a release path

    Choose the environment and approvers to use for each stage of your release. You can add multiple final approvers for each stage if you want to.

    Add the stages and approvers for your release process

  2. Create a release template and use the release path that you just added. Link your build definition to this release template to have access to the build.

    Add a release template

    Next you define the sequence of actions that deploys your app for each stage.

    From the Release Templates page add the deployment sequence

    The deployment agent must have sufficient permissions to perform any of the actions in your sequence. For example, to remove a web site the deployment agent service must run as a local administrator on that machine.

Next steps

  1. Start a new release.
  2. Approve steps in a stage.

Q & A

Q: Can I deploy components of my multi-tiered app separately?

A: Yes, you can create components with separate deployment information.

Configure Apps tab, Components

Add the component to the release template. Now you can add this component to any stage that needs it.

Configure Apps tab, Release Templates, right-click Components and choose Add

Q: What release actions can I add to the deployment sequence?

A: More details on actions are here.

Q: How do I copy a deployment sequence of one stage to another?

A: Use the shortcut menu of a sequence to copy it. Select the sequence where you want to paste it, and use its shortcut menu to Paste Deployment Sequence.

Release template with deployment sequence selected

Go back Back to overview

Help and support

Send suggestions on UserVoice, follow us on Twitter @vsreleasemgmt

or send a smile from the Send-a-Smile link on the menu bar.