可以通过在部署队列设置"区域中进行更改来控制类似行为.切换为部署最新版本并取消其他版本"将自动取消先前排队的版本，并将较新的版本排队.如果您像我一样打开了Slack集成，则会看到取消消息.

Looks like this behavior can be controlled by making a change in the Deployment Queue Settings area. Switching to "Deploy latest and cancel the others" will automatically cancel the previously queued release and queue the newer one. If you have Slack integration turned on (as I do) you will see a cancellation message.

只要您的过程足够简单，以至于您知道何时进行新的构建，就感觉这是良好的行为.它为您提供了基本的手动门，而不会增加任何其他开销.

So long as your process is simple enough that you know when new builds are being made, this feels like good behavior. It gives you a basic manual gate without adding any other overhead.

这里有更多文档: https://docs.microsoft.com/zh-cn/azure/devops/pipelines/process/stages?view=azure-devops&amps=amp=#ic#queuing-policies

部署队列设置:后续版本