CI/CD Implementation For A Simple Web Application Using Azure DevOps - Part Two

This is the article which continuation of the CI/CD implementation for simple web application using Azure DevOps - Part 1, explains how to implement CI/CD (Continues Integration and Continues Delivery) for a simple web application using Azure DevOps. In the previous article, we have covered until the pipeline configuration for a simple web API application. In this article, we will cover the remaining portion of CI/CD.

Release pipelines in Azure Pipelines and Team Foundation Server (TFS 2015.2 and later) help your team continuously deliver software to your customers at a faster pace and with lower risk. You can fully automate the testing and delivery of your software in multiple stages all the way to production, or set up semi-automated processes with approvals and on-demand deployments. For more details, release pipeline management.

So, as of now, we have configured pipeline settings. Let's move to release the pipeline configuration. Click the release menu from the left side menu bar and click on Create a New Release Pipeline.

You will be redirected to release pipeline page, there you can configure artifacts and stages. An artifact is a deployable component of your application. It is typically produced through a Continuous Integration or a build pipeline. So let's configure artifacts like below. You can see the source (build pipeline) in the below screenshot. There you have to select our corresponding pipeline.

The next step is to configure the release stages. Stages are a collection of related jobs, such as the “Build”, “Test”, or “Deploy.” I used stages to build my application, and then target the deployment to multiple environments like (Dev, QA, Staging, Production). To add a new stage, click add a stage button shown in the below screenshot.

Next, we have to select an appropriate deployment service. There are multiple services available to deploy our application. As of now, I am going with Azure App Service Deployment.

In the next step, you have to configure agent jobs and tasks for the particular stage. So, click on the stage that we have created and configure the stage configuration.

Here you can configure jobs and tasks. Let's do a task configuration like below (as we selected Azure Service). Once you select Azure subscription, then click the Authorize button.

You can see that we don't have an app service name listed out. It is because we haven't created an Azure app service for this application. To do that, we need to login to portal.azure.com and create it.