The new Review Apps feature of Azure Pipelines (in preview) allows developers to dynamically create environments on every Pull Request, to test applications consisting of multiple microservices.
Post by this author
During our Connect(); 2017 event, we announced the public preview of Azure DevOps Projects to help customers start running applications on any Azure service in just three steps.
Today, we’re excited to announce that Azure DevOps Projects is now generally available in the Azure Portal,
Since we announced Azure DevOps Projects at the Connect conference late last year, we’ve been hard at work to make it as easy as possible to get set up with a fully functioning DevOps pipeline for your team in a few short steps – regardless of what platform you build your applications in and which features you want to use in Azure.
In today’s world, organizations need to innovate and get to market faster. This requires learning latest technologies, using them in your product and deploying at a faster pace.
Adopting Azure is one such scenario. Existing on-premise apps are getting migrated to Azure and new applications are getting developed to take advantage of Azure services.
In this blog post I will show you how to setup continuous delivery of a dockerized app by using Visual Studio Team Services (VSTS) to a Kubernetes cluster running in ACS.
Azure Container Service (ACS) allows to deploy and manage containers using Kubernetes,
This blog post shows how you can deploy an application from Visual Studio Team Services to Azure Virtual Machine Scale Set. An application running on a VM Scale Set is typically deployed in one of the two ways:
Install new software on a platform image at deployment time by using VM extensions.
Continuous Delivery in Visual Studio Team Services simplifies setting up a robust deployment pipeline for your Web App on Linux. By default, the pipeline builds a container image, pushes the image to a container registry and deploys the new image to the Web App.