Building a CI pipeline for Containerized Asp.NET Core 3.1 using Docker Registry

This is continuation of a series of posts on using Docker and containerization with .Net Core. If you are new to this series its recommend to look at Getting started with Docker and Containers

In this post will show how to setup a pipeline that continuously builds a repository that contains a Docker file. Every time you change your code, the image is pushed to Docker Hub.

Pre requisites

1.     Github account

2.     Azure DevOps Organisation if you don’t have one, you can create for free

3.     Ensure you’re administrator of the Azure DevOps project

4.     Docker hub repository – more details can be found here

5.     Azure Project to be created in Azure DevOps

Get the code from GitHub

https://tinyurl.com/ydtggef6

Create the Pipeline

1.     Sign in to your Azure DevOps Organisation and navigate to your project

2.     Go to Pipelines and click on New Pipeline

3.     Select where is your code from the below screen. In our example its on GitHub. If you’re proficient with YAML choose GitHub YAML where your pipeline can be scripted and for new people to start we will be using classic editor which provides GUI interface.

4.     After clicking on Continue it asks for Built template lets start with empty job template

5.     Navigate to Trigger tab and enable “Continuous Integration” for the respective branch which enables CI on it.

6.     Adding Docker task in pipeline

Note: Docker Task version used here is 2.*

7.     Configure Pipeline task for Container Repository

Save the pipeline all set to go at this point. Now if we trigger a build or code is pushed to repository, In Docker Hub repository we should be able to see the latest image pushed from Azure DevOps.