***NO_CI*** 代表什么？
门控签入将创建一个名称以 ***NO_CI***? 结尾的变更集。 NO_CI 代表什么？我只能想到“没有检查错误”，但这没有意义。
A gated check-in will create a change-set whose name is ended with ***NO_CI***? What is that NO_CI stand for? I can just think of "no check in errors" but it doesn't make sense.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
它代表无持续集成。
由于签入是门控的，现有代码加上此签入将单独构建，并且仅在构建成功后才允许。因此，当门控过程实际将其提交给源代码管理时，签入没有任何意义会导致另一个（持续集成）构建发生，因为此时变更集是“已知的”好的'。
因此，这个后缀是对持续集成系统的指令，其效果是：“当这个变更集实际上‘真正’提交时，不要自动启动基于它的持续集成构建”。
It stands for No Continuous Integration.
Since the check-in is gated, the existing code, plus this check-in, will be built separately and only allowed onwards if the build is successful. So when the gating process actually submits it to source control, there wouldn't be any point for that check-in to cause another (continuous integration) build to occur, since at that point thechangeset is 'known good'.
So this suffix is an instruction to the continuous integration system to the effect of: "When this changeset actually gets committed 'for real', don't automatically fire a continuous integration build on account of it".
签入时的 NO_CI 表示“无持续集成”，即“请不要因为此次签入而启动 CI 构建”。
NO_CI on a check in indicates "No Continuous Integration" i.e. "please don't start a CI build because of this check in".
这意味着在此签入后将不会触发持续集成 (CI) 构建。您必须修改 XAML 文件，以便在门控签入活动完成后触发 CI 构建。
有关如何自定义 XAML 文件的更多信息，请参阅以下链接。
http://donovanbrown.com/发布/如何在门控构建后运行 CI 构建
This means that there will be no continuous integration (CI) build triggered after this check-in. You will have to modify your XAML file so that the the CI build is triggered after the gated check-in activity is done.
Please refer to the following link for more information on how to customize the XAML file.
http://donovanbrown.com/post/How-to-have-CI-builds-run-after-a-Gated-Build
基于此问题，您可以使用
[skip ci]以及提交消息中的以下句子，如 Travis 或 Circle 等其他 DevOps 工具包，...在不需要 CI/CD 管道的提交上跳过 CI 管道（例如更新文档或一些杂务更改）[跳过 ci]或[ci 跳过]skip-checks:true或skip-checks:true[跳过 azurepipelines]或[azurepipelines 跳过][跳过 azpipelines]或[azpipelines 跳过][跳过 azp]< /code> 或[azp 跳过]***NO_CI***based on this issue you can use
[skip ci]and the following sentences in commit messages like other DevOps toolkits such as Travis or Circle, ... to skip doing CI pipeline on commits that do not require CI/CD pipelines (like update docs or some chore changes)[skip ci]or[ci skip]skip-checks:trueorskip-checks:true[skip azurepipelines]or[azurepipelines skip][skip azpipelines]or[azpipelines skip][skip azp]or[azp skip]***NO_CI***