Continuous Delivery for Azure App Services from Azure Portal setting up is just matter of few clicks. Continuous Integration(CI) & Continuous Delivery(CD) capabilities allow us to establish an end-to-end delivery platform. It enables rapid development & deployment of software system repeatedly with minimal manual work. In the previous post – Quickly setup everything you need for develop, deploy and monitor your solution on Azure – Using Azure DevOps Project, we have seen how quickly and easily setup an end-to-end development to delivery pipeline from the scratch using the Azure DevOps Project. In this post, we will explore how can setup Continuous delivery for an App Service directly from the portal.
Start Setting up Continuous Delivery for Azure App Services from Azure Portal:
From the Azure Portal, Navigate the specific App Service for which you want to configure the Continuous delivery, and then select “Continuous Delivery (preview)” option available for the App Deployment.
Click on “Configure” to initiate the configuring your Continuous Delivery Process.
In the next step, you need to validate your App services Code Repository / Provide the repository details and also required to select the application framework.
You can also configure the automated tests to run as part of the build and deployment process. App Service Continuous Delivery configuration allows us to select deployments slot during the app server configuration itself.
You can either create a new deployment slot or choose an existing one for the deployment.
Continuous Delivery for Azure App Services from Azure Portal: Review Dashboard
Once done, the finally initiate the creating the pipeline. It will take a while to set up the overall process during which Azure will configure all the required resources including creating deployment slots, provisioning builds and release definition and initiating a build. You can see all the in the summary dashboard post completion the overall process.
Well! You end to end build and deployment pipeline is ready.
Clicking on the Build Definition, Release definition link will take you the linked VSTS account. You can then go ahead and further edit them.
If you edit and review the release definition, you will find it is getting deployed to Staging First, and then it will be performing a slot swap between staging and production.
In an actual environment, you may like to avoid the auto swap and having a pre-deployment approval process before you proceed to production.
Pre Deployment Approval
You may read my article – DevOps for Bots – Rapid Development, Continuous Integration and Delivery (CI/CD) with Azure Bot Service & Visual Studio Team Services (VSTS) for a deep dive on Continuous Delivery and Release management.
Hope this helps!