Member-only story
DevOps Series: Rollback strategy for Azure YAML release pipelines
Introduction
Azure Pipelines supports continuous integration (CI) and continuous delivery (CD) to continuously test, build, and deploy your code. You accomplish this by defining a pipeline.
Continuous delivery automatically deploys and tests code in multiple stages to help drive quality. Continuous integration systems produce deployable artifacts, which include infrastructure and apps. Automated release pipelines consume these artifacts to release new versions and fixes to the target of your choice.
Rolling back deployment is an important consideration of your deployment strategy. The rollback may be required for various reasons — application functionality not working as expected, performance issues, bug found only in production env etc. If you have built your Release pipeline as classic Release pipeline, you can simply choose an earlier release and do a fresh deployment which resembles to rollback to previous version.
The latest way to build release pipeline is using YAML, which Microsoft also recommends. The YAML pipeline although have advantages over classic pipeline, does not support rollback out of the box. In this article, we will look at some of the strategies to rollback when using YAML pipeline
