问题
I am setting up an Azure DevOps release pipeline with three different stages. As shown in the following screenshot a new release has already started even though the preceding release is still running.
Is there a way to configure a release to complete all its stages before the next in the queue is getting started?
回答1:
For more readable, I will talk based on the pic you shared in the question.
In fact, in the release which has multiple stages, the stages are independent of each other. As you can see about the task job defined for different stages, we can know that the execution for different stages are running independently.
The only connection between each stages is the order of execution which determined by After release and After stage.
And also, as the pic mention below:
As you can see that once the Stage1 of Releae-152 execution finished, the Stage1 of Realse-153 will be executed follow by. As I mentioned in previous comment, only the same execution deployed to the same stage can affect each other. For stage1, the Release-153 can override the stage1 in Release-152.
Since there has several release pipeline in queued, as the default, the server will executed the deployment which in same stage firstly. That's why you see the Stage1 of Releae-153 running firstly than Stage2 of Releae-152.
来源：https://stackoverflow.com/questions/57405813/how-to-configure-an-azure-devops-release-to-complete-all-its-stages-before-start