Visual Studio Team Services Gets Multi-Machine Deployment -- Visual Studio Magazine

Visual Studio Team Services Gets Multi-Machine Deployment

By David Ramel
03/27/2018

Multi-machine deployment with Visual Studio Team Services/Team Foundation Server via deployment groups is now out of preview and generally available.

The new Release Management functionality lets developers orchestrate deployments across multiple servers -- on-premises or via cloud virtual machines -- and allows for rolling updates.

When introducing the feature last May, Microsoft explained a deployment group is a logical group of targets (machines) that have installed agents to coordinate deployments. As these are the same agents already used for builds and releases, the company said developers can use the full task catalog on target machines

"Deployment groups represent your physical environments like single box Dev, multi-machine QA or farm of machines for UAT/Prod," Microsoft said. "They also specify the security context for your physical environments."

Furthermore, Microsoft said, the functionality can be extended by the use of REST APIs for deployment groups and targets for programmatic access.

During the 10-month preview, the company said it saw customers put the functionality to use in various ways, such as:

Deploying to multiple geographic regions or multiple datacenters.
Delivering application updates to multiple customers (multi-tenanted deployments).
Managing transient workloads on clouds by dynamically spinning up deployment targets and tearing them down, or via auto-scaled targets, such as Azure VM Scale Sets.
Performing blue/green deployments with a traffic manager/load balancer.
Scaling deployments from a single server to more than 600 servers in a single deployment group.

Those use cases are likely to be expanded with new features in the generally availability release, which adds: shared deployment targets via deployment pools; new release definition templates; an enhanced Azure Resource Group to boost the provisioning of virtual machines; and more.

Full details can be found in yesterday's (March 26) announcement post.

About the Author

David Ramel is an editor and writer at Converge 360.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.