In the previous article we have seen how to install Microsoft Release Management. In this article we are going to see how to configure environments and release paths.

To start, we need to define the stage types. The stage types are the logical steps required to bring a build from development to production. Go to Administration -> Manage Pick Lists -> Stage Type and add three stages: DEV, QA and PROD.

[caption id="attachment_132" align="alignnone" width="1036"]Manage Pick Lists Manage Pick Lists[/caption]

The next step is to add a new server to Release Management. A server is a machine where a deployment agent is installed. Go to Configure Paths -> Servers, expand the New button and click on Scan for new.

[caption id="attachment_135" align="alignnone" width="1036"]Scan for new server Scan for new server[/caption]

A list of unregistered servers will be shown. Select the server and click on Register

[caption id="attachment_137" align="alignnone" width="882"]Unregistered servers Unregistered servers[/caption]

The next step is to create the different environments to be used in the release path we will define later. Go to Configure Paths -> Environments and click on New

[caption id="attachment_129" align="alignnone" width="1036"]Create Environment Create Environment[/caption]

Fill the general information form. Now, we have to link this environment to a server (remember, a server is a machine with the deployment agent installed). Click on Link existing.

[caption id="attachment_131" align="alignnone" width="882"]Link server Link server[/caption]

Select the server and click on Link. Save the environment and repeat the operation for the QA and PROD environments.

[caption id="attachment_130" align="alignnone" width="1036"]Environments Environments[/caption]

We are ready to configure the release path. A release path is the path used for distributing the software. We can define as many paths as we need (standard, customer emergency, etc). Go to Configure Paths -> Release Paths and click on New.

[caption id="attachment_133" align="alignnone" width="1036"]Release Path Release Path[/caption]

After filling the name and description of the release path, we are ready to configure the stages. Click on Add. Select the stage type from the Stage dropdown. Select the environment associated to the stage from the Environment dropdown. Each step is composed of 3 sequential steps:

  • Acceptance step: the user selected as the approver in the Approver dropdown will be the responsible for approving or rejecting the deployment of the release in the stage. This step can be automated by selecting the Automated check box.
  • Deployment step: is composed of 2 parts:
    • Deployment of the components: the user selected as the approver in the Approver dropdown will have the responsibility of the deployment and he will be notified about it.
    • Validation of the deployment: the user selected as the validator in the Validator dropdown will have the reponsibility to validate that the components have been deployed correctly.
  • Apporval step: the users added to the Approvers list will have the responsibility to aprove or reject the release.

Repeat these steps for all three stages.

[caption id="attachment_134" align="alignnone" width="1036"]Release Path Complete Release Path Complete[/caption]

And that's all for today. In the next article we will see how to configure the deployment of a web site using this release path.

See you soon!

ANTLR and JavaScript

In the last few weeks I've been working on Crystal Gazer, a nodejs console application to gather information from your Git repository. Yo...… Continue reading

Calling a Step Function

Published on July 09, 2017