Azure Devops多阶段管道或发布，何时使用什么? [英] Azure Devops multistage pipeline or release, when to use what?
问题描述
我已经开始使用多阶段流水线进行一些测试，以便能够将流水线作为代码，但是考虑到我们也有Release流水线，以及多路流水线，我对流水线的使用有些困惑舞台流水线目前可以在门和多个环境中完成发布流水线的工作，只是在我希望的基于代码的流水线中.
我的问题是何时应该使用它们中的每一个?
何时应使用它们中的每一个?
在这里，非常同意iberodev和Daniel的任命， YAML是未来.基于大多数开发人员和用户， YAML 是我们在最近的sprint中进行开发工作的重点.
但是，现在，基于它们的功能支持来选择使用需求.
- 通过多阶段使用YAML:
通常，我们建议您将YAML多阶段使用.我们已经为YAML中的大多数UI功能提供了支持，包括管道资源，服务器作业等.
此外，YAML仍然具有一些传统ui管道不具备的功能，例如 Environments 是YAML独有的功能，策略作业，作业输出，模板等.这些都仅支持YAML.
此外，这是我们的 解决方案
When should each of them be used?
Here, very agree iberodev and Daniel's appointment, YAML is the future. Based on most developers and users, YAML is the focus of our development work in recently sprints.
But now, the choice of your use need based on the feature support of them.
- Using YAML with multi-stage:
Most of time, we recommend you use YAML with multi-stage. We have provided support for most of the UI features in YAML, including pipeline resource, server job and etc.
Also, YAML still has some features that classic ui pipelines doesn't, such as Environments is exclusive to YAML, Strategies jobs, job outputs, templating and etc. These are all YAML only supported.
In addition, this is our latest YAML feature announcement document and we are still keeping this doc update once we put the new feature into product. If the features you need in actual use are described in this document. I strongly suggest you use Multi-stage pipeline.
- Using Release pipeline of Classic UI:
BUT, as I mentioned previously, we are developing but haven't support all of the features in YAML. For example, there has one most key feature in classic UI release pipeline, Gate, it is still in progress of developing: Automated checks (gates) between stages.
When this or other feature which haven't added in YAML is necessary in your team, at this time, you'd better use Release pipeline with classic UI for your product security.
这篇关于Azure Devops多阶段管道或发布，何时使用什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
