What's new with Azure Pipelines. We've updated Continuous Delivery capabilities with triggers on other pipelines and Azure Container Registry, and implemented new deployment strategies for VMs and Kubernetes. We're also making Pipeline Caching and Pipeline Artifacts generally available.
Post by this author
We are excited to announce that Deployment Groups is out of preview and is now generally available. Deployment Groups is a robust out-of-the-box multi-machine deployment feature of Release Management in VSTS/TFS.
What are Deployment Groups?
With Deployment Groups, you can orchestrate deployments across multiple servers and perform rolling updates,
Today we are excited to announce the public preview of the new Deployment Groups in Visual Studio Team Services.
Release Management now supports robust in-the-box multi-machine deployment. You can now orchestrate deployments across multiple machines, perform rolling updates whilst ensuring high availability of the application throughout.
This blog post shows how you can deploy a new PHP application from Visual Studio Team Services or Microsoft Team Foundation Server to Azure App Service.
Download the sample
Fork the Hello World sample app repository to your github account
Create a web app
From Azure portal >
Release Management now supports robust in-the-box multi-machine deployment. You can now orchestrate deployments across multiple machines, perform rolling updates while ensuring high availability of the application throughout.
Agent based deployment capability relies on the same build and deployment agents. However, unlike the current approach,
Agent-based deployment in Release Management
Our approach in Release management so far has been to integrate with various deployment tools and platforms while providing rich control over the flow of bits, traceability, and auditability.
When it comes to PaaS deployments, we have first-class integration with Azure,
You have downloaded the Release Management for Visual Studio client, and are connected to either your Visual Studio Online account.
You have an Azure Cloud Service project and want to use Release Management to update the same using the latest drop from a TFS build
In the current state,
With Microsoft Release Management 2013 Update 3 RC, you can now use Windows PowerShell or Windows PowerShell Desired State Configuration (DSC) for deploying and managing configuration data.
Windows PowerShell (PS)
Refer to Scripting with Windows PowerShell (PS) for more details.
Pre-requisites for triggering Chef deployments using RM:
Target node must already be bootstrapped and registered with Chef server
Relevant cookbooks uploaded to Chef Server. Cookbook should have an attribute which maps to build drop location.
Recipes assigned to Node.
Deployment using Chef:
As a first step you need to setup Release Management Server as Chef Workstation.
With Microsoft Release Management 2013 Update 3 RC, you can now use Windows PowerShell or Windows PowerShell Desired State Configuration (DSC) for deploying and managing configuration data. We now support deploying to On-premise environment (Standard) and Azure environments without having to setup Microsoft Deployment Agent.