Angular Apps Continues Integration and Continues Delivery using Azure DevOps
Continues Delivery (CD) has gained more power since DevOps duties have become easy to obtain by developers. In simple terms, Continues Delivery is the constant publish/deployment of asset. Call it REST API, web site, etc. Previously, I showed you how to make a CI Angular app in Azure DevOps. Now, I’ll show you to make a CD for your Angular app.
In your project expand Pipelines, click on Releases, and click on New pipeline (should be in the middle of the screen)
Select Azure App Service Deployment.
Before we step into the tasks. Let’s focus our eyes in the little box that is before the stages box. On the Artifacts box we define which build pipeline we want the CD to start with. In other words we tell the next step this is the artifact I want you to deploy. The artifact is of course is the one we setup in the previous step. So we select Angular App DEMO – CI. After entering all the data we click on add.
To make it continues we now click on the little thunderbolt
We enable Continues Deployment trigger
We have configured the continues part. Let’s focus on the Stage 1 box. click on 1 job, 1 task. It will take you to the following screen
Change the state name to whatever appropriate name conventions are you using. Select your Azure subscription (how are we going to pay for it). Select you App type, which in our case is a Web app on Windows. Then, select the App service that you previously created in your Azure postal.
The next step is to select the package or folder where the artifact is. Don’t forget to change the name of the task as well as making sure you select where the artifact is.
Finally change the name of the pipeline and save.
CONGRATULATION! you have a CD pipeline for you angular app!
Just make a change in your code and push it to master fort he CI to build it and CD to deploy it.