Continuous integration and continuous delivery (CI/CD) With DevOps Azure
Continuous integration and continuous delivery (CI/CD) are considered by most to be the backbone of DevOps. Starting CI/CD With DevOps Azure get really interesting when you combine these practices with programmable infrastructure and a suite of services that allow you to automate the entire lifecycle of an application.
Create Your Azure DevOps Organization
The first step starting CI/CD with DevOps Azure is to navigate to dev.azure.com and sign in to Azure DevOps. If you’ve never done this before, you’ll need to create a new organization. If your already have an organization you may skip this step.
Setting Build Pipeline for Azure
Go to your Azure DevOps and click on Builds. Look like figure 1 below.
Click on new pipeline to start build from your repository. Now you should see an option to select where your code is available. You can choose accordingly.
As my project is in GitHub repository, I will select that. Please note that I will be using the classic editor to create the pipeline now, so that I can show the steps with the screenshots.
After choice you will be ask to select pipeline configuration. For ther project i use a PHP project from my repository.
You should be able to see the final yml file at the end of the configuration.
If you’re not using composer you may delete the scripts. For this purpose i’ve using default azure-pipelines.yml configuration. If no other setup you may save and run the yml and starting commit to your repository.
As everything is already created for us, let us save and queue the build. Please make sure that your source code branch is valid and you have verified the build. After you save and run your pipelines is already running like figure below.
After build success you may see the pipeline already done like figure below Now your build is complete. Notice that a lot went on with the build. The service used an Ubuntu 16.04 build agent to grab the code from GitHub, installed our development dependencies, and then ran our unit tests to validate the application. Finally, the code was bundled into an output artifact and published so we can use it as an input artifact for our upcoming release pipeline. You may get the status badge on toogle button at the top of the pages and place it to your repository.