Release your app to environments with deployment agents

If you want to use Windows PowerShell, Windows PowerShell Desired State Configuration (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, connect to release management and add stages for your release. For details, see this topic.

Set up servers and environments

  1. Install and configure a deployment agent to any machine that will be part of the environment used to deploy your app. See Install deployment agent and set up machines for an environment for more details.

  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 new servers that already have agents

  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 servers to use for your environment

  4. Create environments for each of your stages. Link the servers to your environments. An environment can contain multiple servers.

    Link the servers to your environments

Create a release template

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

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

    Create a release path

  3. 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.

    Choose the environment and approvers

  4. 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.

    Create a release template to use the release path

  5. Define the sequence of actions that deploys your app for each stage.

    Define the sequence of actions to deploy the app

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. See the section “Start a release” in this topic.

  2. Approve steps in a stage See the section “Approve steps in a stage” in this topic.

Q & A

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

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

Create components with deployment information

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

Add the component to the release template

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.

Copy a deployment sequence between stages