Azure DevOps中的构建管道和发布管道之间有什么区别? [英] Whats the difference between a build pipeline and a release pipeline in Azure DevOps?

问题描述

我已经通过使用 .yaml 文件在 Azure DevOps 中建立了多个多阶段的构建管道.我已经阅读了有关可用的发布管道"的信息，我想知道这些管道有什么好处?

I have set up several multi-staged build pipelines in Azure DevOps by using .yaml files. I've read about the "Release Pipelines" available, and I'm wondering what the benefits of those are?

他们似乎在做同样的事情，甚至没有提供.`YAML的支持.那么，这里的主要区别是什么?我可以通过使用发布管道而不是通常的构建管道来做什么?

They seem to do the same, don't even offer .` YAML's support. So what's the main difference here? What can I do by using release pipelines, rather than usual build pipelines?

推荐答案

在Azure DevOps中，在存在多阶段yaml管道(现在称为"管道""之前，通常使用 Build 管道以 build /创建软件二进制文件(例如，dotnet publish或ng build --prod)并存储了这些工件在Azure DevOps放置位置.

In Azure DevOps, before there was the multi stage yaml pipelines (now known as "Pipelines", you usually used the Build Pipeline to build / create your software binaries (e. g. dotnet publish or ng build --prod) and stored these artifacts in the Azure DevOps drop location.

然后，您通常有一个 Releasee 管道，该管道会被这些构建工件(软件二进制文件)触发，并部署到一个或多个阶段.

Then you normally had a Releasee Pipeline that gets triggered with these build artifacts (software binaries) and deploys them to one or many stages.

将这两个管道(构建和发布)分开的原因是，您只想一次构建特定版本的软件，然后使用 相同> 在您的每个目标环境(例如，开发/测试/生产)中的二进制文件.

The reason to separate these two pipelines (build and release) is that you want to build a specific version of your software only once and then use the same binaries in each of your target environment (e. g. dev / test / production).

使用新的管道，通常使用第一个 Stage 来构建工件，然后使用下一个阶段部署-与之前但在一个模块中.

With the new pipeline, you usually use the first Stage to build your artifacts, and the next Stages to deploy it - similar as before but in one module.

如果您以前使用过构建&发布管道，您将在新的Pipeline模块中看到旧的构建定义，并在旧的发布模块中看到旧的发布定义.但是，他们从未将YAML引入发布管道，因为他们知道他们仍然会用多阶段管道替换它们.

If you have previously used the build & release pipeline, you will see the old build definition inside the new Pipeline module, and the old release definition in the old release module. However, they never brought YAML to the Release Pipelines because they know that they will replace them with the multi stage pipelines anyway.

结论:如果您使用新的多阶段"管道"模块，则不再使用经典的发布管道.

Conclusion: If you use the new multi-stage "Pipeline" module, you shouldn't use the classic Release Pipelines anymore.

这篇关于Azure DevOps中的构建管道和发布管道之间有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！