How we use RM – Part 1

The teams that contribute to VSTS (TFS and other micro-services like Release Management, Package Management, etc) began using Release Management to deploy to production as outlined by Buck Hodges in this blog. However, in Feb this year, there was some feedback that it was difficult to debug failed deployments using RM, and that engineers were… Read more

Configuring your release pipelines for safe deployments

For large and high scale applications, the promise of “enterprise grade” availability and high reliability levels are key to customer confidence on the applications. Continuous delivery pipelines for such scaled out applications typically consist of multiple environments. DevOPS enables faster & automated delivery of changes, thereby helping customers with the most advanced set of features…. Read more

Deploy PHP application to Azure App Service using VSTS

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 > App Services > + Add Select… Read more

Deploy Node.js applications to Azure App Service

This blog post shows how you can deploy a new Node.js application from Visual Studio Team Services or Microsoft Team Foundation Server to Azure App Service. Code Download our Node.js Hello World sample app or Install Node.js Tools for Visual Studio and create a new Node.js application. Upload your code to Team Services or your… Read more

Building Your App in a CI Pipeline with Customized Build Servers (Private Agents)

With the expanding number of tools to help you become more productive or to improve the functionality of your app, you may have a requirement for a custom tool or specific version to be used during the build process in a Continuous Integration build. If using Visual Studio Team Services, there may be instances when… Read more

Deploying to On-Premises Environments with Visual Studio Team Services or Team Foundation Server

I hear this particular question frequently as a reason teams are concerned about adopting Visual Studio Team Services when their applications still run on-premises.  The good news is that it is typically a quick walkthrough on how build & deployment pipelines work.  I want to give a big thanks to Sachi Williamson from Northwest Cadence… Read more

Managing Configuration and App Settings for Multiple Environments in Your CD Pipeline

Your continuous delivery pipeline typically consists of multiple environments. You may want to deploy changes first to a test or staging environment before deploying to a production environment. Furthermore, your production environment may itself comprise of multiple scale units, each of which you may deploy in parallel or one after the other for a gradual… Read more

Integrating Smoke Tests into your Continuous Delivery Pipeline

We’re really glad to have Abel Wang help us out for #SpringIntoDevOps with this awesome blog contribution about verifying whether your deployment finished successfully by integrating smoke tests into your pipeline.  Thank you Abel!  — Ed Blankenship Having a Continuous Integration (CI) and Continuous Delivery (CD) pipeline in Visual Studio Team Services enables us to build… Read more

VSTest task dons a new avatar – testing with unified agents and phases

Visual Studio Test (VSTest) and the Run Functional Test (RFT) tasks are used widely for continuous testing with Team Build and Release Management. As we thought about how test execution in the pipeline should evolve the guiding principles were to ensure that test execution in the pipeline is fast and reliable for all types of tests, be… Read more

Agent-based deployment in Release Management

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, where you install the build and deployment agents on a set of proxy… Read more