Ask Learn
Preview
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Modern Lifecycle Development requires teams to be agile and work with a DevOps mindset. To realize that vision fully, it is paramount to have a robust release pipeline for managing the releases. Release Management vNext is a VSTS service that enables teams to automate the deployment of their applications in different environments and manage releases effectively with great traceability. RM vnext service makes it possible for teams to do continuous integration and continuous delivery with a sophisticated approval and configuration management workflow. RM vNext is in the Public Preview stage currently.
In this blog post, I will demonstrate using RM VNext for an OnPrem deployment using On Prem Build/Release Agents set up. We will be deploying a simple MVC application which will be packages as a zip file for Web Deploy deployment using OOB IIS Deployment Task. We will set up both Continuous Integration and Continuous Deployment for this sample application.
1- Create a Visual Studio VS 2013/2015 ASP.Net Web Application.
2- Once the project is created, check in the Solution into the appropriate VSTS Team project. It is assumed here that you have a VSTS project in place.
Next we will work on the Release part for Deploying the Application to an On Prem Environment using Release Management. We need to go to the Release TAB.
There are options for Pre-Deployment and Post-Deployment Approval. Agent options allow you to configure the Agent for release. The agent you configured for Build can be used for Release as well. You can also use Configure Variables option for tokenization of certain configurations which are environment specific.
Keeping in mind when working on Prem Deployment, the Build/Release Agent needs to be configured on an On Prem Machine so that they have clear line of sight to the servers which need to be deployed which are on Prem as well.
For enabling this, we need to create Deploy Machines which is a machine group which makes it easy to do the deployment. You can also specify the machines using the Machine IP’s or FQDN with ports but Machine group is recommended.
This will ensure Release to the environments when build is kicked off and completed.
Here is how the Build and Release Summary reports look. Great insight into the Changesets, Associated Work Items, Test cases run, Code Coverage reports.
You can also check out https://msdn.microsoft.com/library/vs/alm/release/overview for more information. Happy Releasing using RM Vnext service
Anonymous
February 12, 2016
Hello, the IIS tasks are not available for me in VSTS. Is it necessary to download it?
Anonymous
February 13, 2016
The comment has been removed
Anonymous
February 14, 2016
Awesome. Thanks for the reply Monu!
Anonymous
June 29, 2016
Great tutorial. However one question / suggestion: In point 3.1 you mention to configure the Visual Studio Build task. I can see in the screenshot that you have configured some parameters. However they are not all captured fully by the screenshot. Can you maybe give a complete list of all the needed parameters? Maybe possibly elaborate a bit more detailed about each of them as well (which is just easy for me, but I can also look each of them up).
Anonymous
November 07, 2016
I thereI would also like to get an insight about the MSBuild parameters,please!
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign in