如何配置Azure DevOps版本以在开始新版本之前完成其所有阶段 [英] How to configure an Azure DevOps release to complete all its stages before starting a new one

问题描述

我正在建立一个具有三个不同阶段的Azure DevOps发布管道.如以下屏幕截图所示，即使先前的版本仍在运行，新版本也已经开始.

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?

推荐答案

为便于阅读，我将根据您在问题中共享的图片进行讨论.

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.

而且，如下图所示:

您可以看到，一旦 Releae-152 的 Stage1 执行完成， Realse-153 的 Stage1 strong>将被执行.正如我在前面的评论中提到的那样，只有部署到同一阶段的同一执行才能相互影响.对于stage1，Release-153可以覆盖在Release-152中的stage1.

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.

由于队列中有多个发布管道，因此默认情况下，服务器将首先在同一阶段执行部署.这就是为什么您看到 Releae-153 的Stage1比 Releae-152 的Stage2优先运行的原因.

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.

这篇关于如何配置Azure DevOps版本以在开始新版本之前完成其所有阶段的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！