Should i use Azure release pipeline for deployment or directly deploy from build pipelines by using a task?

1.1k Views Asked by At

Azure DevOps has Pipelines (build) blade and Releases blade, deployment can be done by both either by creating a specific task in the build pipeline or by creating a new release in Releases, which one should i use?

I used both solutions and i belive using Releases is the cleaner approach

1

There are 1 best solutions below

2
Ceeno Qi-MSFT On

I suppose that in your scenario, it's better to use release pipeline, as you could separate the building process and deploying process into different workflow.

If your artifacts are still under the debugging, you could just put it in the building pipeline without the deployment process. After you put the artifacts into deployment, when you need to optimize the artifacts, you only need to test in the build pipeline and won't effect the current success deployments. After you finish the debug, you only need to edit the artifact version in the release pipeline. enter image description here

Even if you change the artifacts source for the deployment, you only need to change the artifact source and you don't need to create the deployment process again in single pipeline. enter image description here

And once the debug has completed, you could use the release blade to test the artifacts in different deployment environments, without the building process(usually the building process would cost quite long time, especially when you have multiple artifacts).

Especially when you need to deploy the artifacts in different environment, creating the parallel stages could help you troubleshoot the stages one by one for different errors. Even one stage fails, the other deployments would still continue. enter image description here enter image description here