Azure DevOps:为什么新管道将yaml文件提交到默认分支 [英] Azure DevOps: Why does new pipeline commit the yaml file to default branch

问题描述

我在Azure DevOps中创建了一个新管道，并为其创建了一个新分支.

I created a new pipeline in Azure DevOps, and created a new branch for it.

结果，DevOps自动将新管道的YAML文件提交到我的开发"分支.

As a result, DevOps automatically committed the YAML file for the new pipeline to my 'development' branch.

我创建的其他管道都没有将YAML文件提交到存储库中...

None of the other pipelines I've created have YAML files committed into the repo...

为什么要这样做?

我们必须将YAML文件保存在那里吗?

Do we have to keep the YAML file there?

它与应用程序的源代码无关，因此似乎不知道为什么将其存储在其中.

It has nothing to do with the source code of the application, so doesn't seem to make sense why its stored there.

推荐答案

YAML是用于部署应用程序的代码，因此它是源代码的一部分.通过将其置于源代码控制之下，它可以跟踪版本更改以及对在构建过程中确定或插入的参数或变量的任何其他更改.

YAML is code for how your application is deployed, thus it is part of the source code. By putting it under source control it can keep track of version changes and any additional changes to parameters or variables that are determined or inserted in the build process.

这与通过UI而不是源代码控制进行更新并且没有同行评审，分支合并以及可以应用的其他策略的较旧的处理方式相反.

This is opposed to the older ways of doing things where it was updated via UI and not source control and did not have peer reviews, branching merging, and additional polices that can be applied.

在之上YAML发布管道将于上周正式发布，这将使YAML在回购协议下更加强大，因为YAML不仅会构建代码，而且还会发布代码.

This on top of the the YAML Pipelines for Releases going GA the other week will make YAML under a repo even more powerful as the YAMLs will not only build but also release code.

这篇关于Azure DevOps:为什么新管道将yaml文件提交到默认分支的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！