At the moment, we’ll look right into a CI/CD pipeline answer. We’ll take a look at the method from logging a job to coding after which constructing and deploying to the vacation spot utility. We’ll take a look at Azure DevOps because the platform for all this course of after which deploy the applying to an Azure App Service as an internet utility.
We’ll begin with the diagram offered by Microsoft. Particulars can be found on the Microsoft web site beneath,
Parts of the design
The diagram begins with the Engineer. This may be the DevOps engineer, Scrum Grasp, or developer. All duties and points are saved within the Azure DevOps Backlog. This can be a record of all new options, bugs, enhancements, and so on., that should be labored on by the crew. Different options for this embody the JIRA platform, which is used to retailer and monitor points. The code for the applying is taken from the Azure Repo, which is primarily a Git repository and is labored on by the developer. As soon as the repair is full, the code is saved to the repository, primarily within the respective department created for the actual job. As soon as the code is merged again into the principle department, it mechanically triggers a construct within the Azure DevOps construct pipeline. This course of may also be manually triggered if required. As soon as the construct course of is full, which may additionally embody exams, the code is deployed to the Azure App service through the Azure DevOps launch pipeline. Relying on the requirement, this course of may also be triggered manually or mechanically. The code is generally deployed right into a testing or UAT slot. Right here, the adjustments are examined, and if all appears to be like good, the slot is swapped with the manufacturing slot, and the adjustments are prepared to be used in manufacturing.
It’s at all times a good suggestion to arrange monitoring of our utility utilizing Software Insights. From right here, we are able to gather real-time knowledge on the utilization, efficiency, and any points on our utility. As soon as these are collected, we are able to document them again into our Azure DevOps Backlog and begin the method yet again. This course of is generally run in Agile sprints the place a sure variety of duties are assigned to builders for a sure period of time, e.g., two or 4 weeks, and this is named the dash cycle.
In at present’s article, we checked out easy methods to design a CI/CD pipeline answer for our utility deployed in Microsoft Azure utilizing Azure DevOps. Different alternate options can be found, like GitHub actions, and so on. Nevertheless, I like to recommend utilizing the whole Microsoft stack and Azure DevOps for an Azure utility.