在天蓝色背景下，管道和释放管道的区别是什么？

当您选择如下所示的选项时，将生成 yaml 文件:

enter image description here

在这个 yaml 文件中，您可以定义从 restore -> build -> run tests -> publish and -> deploy to azure app service web app开始的整个部署周期。

那么，为什么还有释放选项呢？如果我可以通过 Pipelines -> Pipelines选项定义整个生命周期，那么 Pipelines -> Releases选项的目的是什么？

enter image description here

36860 次浏览
小开

Pipelines is a name in latest DevOps user interface for Builds. In old UI it's like this: enter image description here

It can be said that Pipeline(or Build, or Build Pipeline) represents CI (continuous integration) in Azure DevOps. Release represents CD(continuous delivery) in Azure DevOps. Pipeline usually takes code, builds it, tests and creates an artifact. Release takes the artifact and releases/deploys it.

The usage depends on your project.

If you have a small project and there is no need in Release features (e.g. pre-deployment conditions and approvals), then you can have Pipeline like you mentioned: restore -> build -> tests -> deploy and no need in Release.

If your project is big with a lot of developers contribution, it's good to have Pipeline which builds, runs unit tests, does other automation and results with artifact every time developer pushes to the common repo. So you can be sure all is settle and integration tests passed. Pipeline also can end up with release/deploy task to development environment/servers for internal work, usage, testing.

In large project you don't need to deploy every push to common repo. So you can settle a Release which will be responsible for deployment to production environment. It has features designed for this, like pre-approval, so everyone is agree it's the right build (or artifact) for production.

小开

As noted in Microsoft docs, the "Releases" section is their "Classic editor" solution: Link

"Pipelines" section offer to create pipelines in two ways:

  1. YAML code
  2. Classic UI editor

What Classic basically means by them is the original way Azure DevOps pipelines are created. You build a pipeline by using a GUI editor in an interactive way. Pipeline created from YAML, with the help of the assistant is the newer way.

What "Pipelines" section mainly have that "Releases" doesn't is that by writing YAML code it enables you to configure your CI/CD strategy as code, where, the Pipeline definition lives alongside and together with your code.

Their newest learning resources also indicate to use YAML and create build and deployment stages in the same pipeline Deploy applications with Azure DevOps

I recommend:

  • If you prefer to use Classic UI editor use "Pipelines" section for builds and "Release" section for deployments;
  • If you prefer to use YAML, just use "Pipelines" section for builds and deployments and create a multistage pipeline.

Pipeline with multiple stages

Edit: Update May 11, 2020, Pipelines YAML CD features now generally available

小开

A Release represents continuous delivery(CD) in Azure DevOps.

A pipeline usually takes code, builds it, tests, and creates an artifact. Release pipelines takes the artifact and deploys it.

Note : If you're using Multi-stage pipeline, you don't need to use the Release(UI) Pipelines. You can define CI/CD steps in one xx.yml file.


提交答案