In Part 1 of the blog series , we created the build configuration for CI/CD pipeline of ARM template deployment. In this blog, we will create the release pipeline and deploy the VMs across dev and test environments in Azure when a commit is triggered
Create the release pipeline by clicking on the release option once the build is completed
In the Release definition, select a blank template to start with
And provide name of your first environment
Now we have our first environment ready, lets add the tasks. Select the created environment.
Start adding tasks from Tasks->Deploy->Resource Group deployment
Edit the settings of the added task. You need to add your Azure subscription to VSTS as a service endpoint
Click on Manage and it will open the service end point configuration in a different tab. Add your Azure subscription here.Click on New Service Endpoint->Azure Resource manager
Add Subscription name , when you click ok you will be ask to login to your Azure subscription to authenticate.
Once that is done, Your subscription will be listed in the release task drop down list and you can select it
Select action as "Create or update resource group".Select the target resource group and the location, which is essentially the target Azure region, from the drop down list. Select template location as linked Artifact.
Browse and select the ARM JSON file from the linked artifact
Depending on the Target environment select the parameters JSON file as well.Select deployment mode as incremental.
Save settings once done
Now you can add the next environment to the pipeline. Click on the plus sign below the existing environment
Provide a differentiating name
Add the deployment tasks like it was done for the first environment. You can change the subscription/resource group/location etc to differentiate it from the dev environment. Also the parameter file should be selected as per the target environment.
Save the changes and with that the release configuration is completed. This is how the continuous deployment pipeline will look like
If you click on the pre-deployment condition for the environments, it will be configured to be auto triggered. For eg, the test environment deployment will be triggered once the dev environment deployment is completed. You can also choose to change it as per your release process requirement
Every time the code is committed in the source repository, the Continuous integration trigger in the build config will start a build. The artifacts of this build includes the JSON file and the target environment parameter files. The continuous deployment process is defined in the release process, which will be auto triggered after the build is completed.
Depending on the target environment settings, the template will be deployed in multiple Azure environments.
PS: If you are interested in Cloud Automation, do check out my book on Azure Automation available in Amazon : https://www.amazon.com/Azure-Automation-Using-Model-Depth/dp/1484232186/ref=tmm_pap_swatch_0?_encoding=UTF8&qid=1513676067&sr=8-2
Create the release pipeline by clicking on the release option once the build is completed
In the Release definition, select a blank template to start with
And provide name of your first environment
Now we have our first environment ready, lets add the tasks. Select the created environment.
Start adding tasks from Tasks->Deploy->Resource Group deployment
Edit the settings of the added task. You need to add your Azure subscription to VSTS as a service endpoint
Click on Manage and it will open the service end point configuration in a different tab. Add your Azure subscription here.Click on New Service Endpoint->Azure Resource manager
Add Subscription name , when you click ok you will be ask to login to your Azure subscription to authenticate.
Select action as "Create or update resource group".Select the target resource group and the location, which is essentially the target Azure region, from the drop down list. Select template location as linked Artifact.
Browse and select the ARM JSON file from the linked artifact
Depending on the Target environment select the parameters JSON file as well.Select deployment mode as incremental.
Save settings once done
Now you can add the next environment to the pipeline. Click on the plus sign below the existing environment
Provide a differentiating name
Add the deployment tasks like it was done for the first environment. You can change the subscription/resource group/location etc to differentiate it from the dev environment. Also the parameter file should be selected as per the target environment.
If you click on the pre-deployment condition for the environments, it will be configured to be auto triggered. For eg, the test environment deployment will be triggered once the dev environment deployment is completed. You can also choose to change it as per your release process requirement
Every time the code is committed in the source repository, the Continuous integration trigger in the build config will start a build. The artifacts of this build includes the JSON file and the target environment parameter files. The continuous deployment process is defined in the release process, which will be auto triggered after the build is completed.
Depending on the target environment settings, the template will be deployed in multiple Azure environments.
PS: If you are interested in Cloud Automation, do check out my book on Azure Automation available in Amazon : https://www.amazon.com/Azure-Automation-Using-Model-Depth/dp/1484232186/ref=tmm_pap_swatch_0?_encoding=UTF8&qid=1513676067&sr=8-2
Comments
Post a Comment