Another prerequisite to getting VS Release Management to automate release workflow is setting up the Servers & Environments. To register as a Server in VS Release Management, machine should be first installed with Microsoft Deployment Agent.
Note - The above view in Configure Apps only available until all mandatory steps are done only. It disappears after all mandatory configurations are once done. Items shown in above can be accessed in different tabs and section in the release management client.
1. Registering Server
In VS Release Management Client click on Configure Apps –> Add Servers link or Click on Configure Paths –> Servers
Click on New –> Scan For New to find available Deployment Agent installed and configured machines.
Optionally enter a prefix or suffix and Click on Register button to register the server found.
Machine get registered as a server and initially shown as offline.
Once the heartbeat is received from deployment agent to release management server, machine shows as ready.
Next step is creating environments, with successfully registered servers.
2. Setup environment
Click on Environments link in Configure Apps or in Configure Paths click on Environments.
Click on New to create new environment.
Provide a Name and click on Link Existing to link registered servers to the environment.
Select the available server(s) and click Link.
You can add tags. These tags are useful when setting up release templates. The tag can be used instead of Server name which allows copying templates workflow steps easily between different stages in the release template.
First environment is created as DevInt (Dev. Integration)
Stage Type Security can be used to restrict the stages in release path that the environment can be used.
For demo purpose QA and Production environments set up with same Server. In practical scenario these will be different servers. and environment may contain multiple servers linked.
Servers and Environments configuration is successfully completed.
Resolve MSB4019: The imported project "C:\Program Files\dotnet\sdk\1.0.0-rc4-004771\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found or Unable to start the process. No executable found matching command "dotnet-projectmodel-server"You might encounter compilation error in Visual Studio 2015 when a new .NET Core 1 web app is created, if you have installed Visual Studio 2...
This extension “ Chamindac.vsts.release.task.download-artifacts ” for VSTS and TFS 2015.2.1 upwards, can be used to filter for build artifac...
It is great if the latest updates to TFS can be applied as and when they are released. But for a large organization it might not be sometime...
There was a question from a team member how to bulk edit TFS work items. In the past the only answer to this question would be use excel. Op...
Let’s look at steps required for Setup Test Farm, Start and Stop, and Test Clients for Test Execution for setting up a Test Farm as Azure VM...