Azure Devops 多阶段管道或发布，何时使用什么? [英] Azure Devops multistage pipeline or release, when to use what?

问题描述

我已经开始使用多阶段管道进行一些测试，以便能够将管道作为代码使用，但考虑到我们也有 Release 管道以及多级管道，我对管道的使用感到有些困惑.阶段管道目前可以在门和多个环境中完成发布管道的工作，只是在我更喜欢的基于代码的管道中.

I've started doing some testing using multi-stage pipelines to be able to have the pipeline as code, but I'm getting a bit confused about the usage of the pipeline considering we have Release pipeline as well, and multi-stage pipeline currently can do the release pipeline's job with gates and multiple environments, just in a code based pipeline which I would prefer.

我的问题是什么时候应该使用它们?

My question is when should each of them be used?

推荐答案

什么时候应该使用它们?

When should each of them be used?

我非常同意 iberodev 和 Daniel 的评论，即 YAML 是未来.基于大多数开发者和用户的需求，YAML 一直是我们近期 sprint 开发工作的重点.

I strongly agree with iberodev's and Daniel's comments, that YAML is the future. Based on the needs of most developers and users, YAML has been the focus of our development work in recent sprints.

但到目前为止，您应该根据各自支持的功能来选择使用什么.

But as of now, your choice of what to use should be based on the features supported by each.

• 在多阶段使用 YAML:

大多数时候，我们建议您在多阶段管道中使用 YAML.我们已经为 YAML 中的大部分 UI 功能提供了支持，包括管道资源、服务器作业等.

Most of time, we recommend you use YAML in multi-stage pipelines. We have provided support for most of the UI features in YAML, including pipeline resource, server job and etc.

此外，YAML 还具有一些经典 ui 管道不具备的功能，例如 Environments、策略作业、作业输出、模板等.这些都仅在 YAML 中支持.

Also, YAML still has some features that classic ui pipelines don't, such as Environments, Strategies jobs, job outputs, templating and etc. These are all only supported in YAML.

此外，这是我们的 最新的 YAML 功能公告文档，随着我们将新功能添加到产品中，我们仍在保持此文档更新.如果本文描述了你需要投入实际使用的特性，我强烈建议你使用Multi-stage pipeline.

In addition, this is our latest YAML feature announcement document and we are still keeping this doc update as we put new features into the product. If the features you need to put into actual use are described in this document, I strongly suggest you use Multi-stage pipeline.

• 使用经典 UI 的发布管道:

但是，正如我之前提到的，我们正在开发但尚未支持 YAML 中的所有经典功能.例如，经典 UI 发布管道中的一项关键功能 Gate，它仍在开发中:阶段之间的自动检查(门).

BUT, as I mentioned previously, we are developing but haven't supported all of the classic features in YAML. For example, one key feature in classic UI release pipelines, Gate, it is still in progress in development: Automated checks (gates) between stages.

当您的团队需要此功能或其他尚未添加到 YAML 中的功能时，您最好使用带有经典 UI 的发布管道来确保产品安全.

When this or other features which haven't been added in YAML are necessary for your team, then you're better off using Release pipeline with classic UI for your product security.

这篇关于Azure Devops 多阶段管道或发布，何时使用什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！