Member-only story
Azure Release Pipelines-DevOps
A Release Pipeline consumes the Artifacts and conducts follow-up actions within a multi-staging system.
A blue/green deployment is a deployment strategy in which you create two separate, but identical environments. One environment (blue) is running the current application version and one environment (green) is running the new application version.

Using a blue/green deployment strategy increases application availability and reduces deployment risk by simplifying the rollback process if a deployment fails.
Once testing has been completed on the green environment, live application traffic is directed to the green environment and the blue environment is deprecated.
A Build Pipeline is used to generate Artifacts out of Source Code. A Release Pipeline consumes the Artifacts and conducts follow-up actions within a multi-staging system.

Let’s see the release pipeline hands-on 👇
Pipeline → release pipeline → new pipelinev → azure app development