Setting up CI and CD pipeline in Azure DevOps for ASP.NET Core and Azure Web Apps

- January 20, 2019

In the last post I talked about Azure DevOps, now we will look into a practical use case of Azure DevOps where we will setup a complete continuous integration (CI) and continuous deployment/delivery(CD) pipeline for a ASP.NET Core project hosted on Azure Web Apps. We will host our project solution on Azure Repo. The basic idea is that we will create an Azure Web app, setup our project on Azure Repo, create CD & CD pipeline on Azure DevOps, and see things in action when we push our code to master branch. Let's get started:

Open Azure portal and go to App Services and click on Create app service.

From the Marketplace templates, choose Web App.

Click Create.

Choose an app service name that is available, select OS be Windows, Publish by code, then choose an app service plan that fits your budget and click Create.

Once the service is deployed, you will get a ntoification, open it and click Go to resource.

Here you can see live link to your azure web app service. Click and open the link.

By default azure web app hosts a default html page indicating its hosted on azure service app. We are pretty much done here with Azure service app.

Now lets setup our project on Azure Repos. Open Azure Repos, if you don't already have an organization go ahead and click on New Organization and once you have created one Click on Create project.

Give the project a name and descripiton, keep it private and then click on Advanced.

Chose a version control system (Git is the most popular so I always choose that) and then choose a working process like Agile or Scrum and click Create.

This will create a repository and take you to its summary page like the one below.

Goto Repos > Files then you will see a link to your repository. You can also directly clone this repo on your Visual Studio IDE. Choose Visual Studio and click Clone in Visual Studio.

This will open up your visual studio, ask you to login via OAuth OpenId process and once clone on your PC, you will see something like that on Solution Explorer windows. We can see that we are connected to a remote repository's master branch.

Now we will add a new ASP.NET Core solution on our local master branch. Go to File > New > Project and under the Installed > Visual C# > .NET Core choose a ASP.NET Core Web Application and a name for the project. Make sure the path is pointing inside clone repository.

Select Web Application (Model-View-Controller) and click OK.

Open Team Explorer, if you have any bin, obj or vs folder items you need to add them to git ignore file. Commit and push the changes with a message.

Go back to Azure DevOps portal of your project and click on Pipelines. Then New pipeline.

Select a source, in our case Azure Repo Git. Select your project, repository and branch. Click Continue.

Select Azure Web App for ASP.NET and click Apply.

Choose a name, select Agent pool, selection all .sln files, select the Azure Subscription on which Azure Web app was create and click Authorize.

Your browser might show you an error notification saying to enable pop-up notification as shown below.

Click on notification icon and select to show pop-up notification always then click Done.

Once you authorize and give access to Azure Subscription, you will be able to see all Azure App service in the drop-down below. Finally click Save & queue.

Click on Save & Queue again while selecting Hosted VS2017 and master branch.

This will setup CI & CD pipeline and your build is schedule for compilation, release and deploy.

Once build is successful, you will see a green tick showing all build steps have been successful. Click on the check-in to see logs.

We can see that all jobs have been successful including Azure App Service Deploy. Ideally, we should have deployed it to a pre-release/pre-deploy slot to make sure everything works correctly but for the purpose of demo I have chosen to directly deploy on web app service which will cause a down time, you should always deploy to Slot first and then swap it with production build.

Now if we open the link to our Azure Web app, we can see latest build is deployed with our check-in

There are much more details that you can find here. The demo was for a quick demonstration of the how you can setup CI & CD pipeline with ASP.NET Core and Azure Web Apps.