为什么*** NO_CI ***仍会导致连续的内嵌构建? [英] Why is ***NO_CI*** still causing a continuous intregration build?

问题描述

我最近发现了TFS的隐藏功能"，如果您的评论中包含***NO_CI***，它可以防止启动CI构建.

I've recently discovered the "hidden feature" of TFS that allows you to prevent a CI build from kicking off if your comment contains ***NO_CI***.

我在家中运行TFS，这个小窍门就像一个咒语.

I have TFS running at home and this works little trick works like a charm.

在工作中，我们还使用TFS2010.我发现这仍然不能阻止CI构建在我们的设置中启动.

At work we are also using TFS 2010. I'm finding that this still does not prevent CI builds from kicking off in our setup.

我的问题是，实际上哪个进程检查注释中是否存在***NO_CI***以确定是否阻止CI构建?我最初的想法是查看构建模板.我没有看到任何明显的东西.有人遇到过这个吗?你能指出我正确的方向吗?

My question is, what process actually checks to see if ***NO_CI*** exists in the comment to determine whether or not to block the CI build? My initial thought was to look at the build template. I didn't see anything too obvious. Has anyone ran into this? Can you point me in the right direction?

推荐答案

这个问题原来是我的错误.构建成功后，我将提交几个自动检入程序.第一个包含***NO_CI***，第二个不包含.我还没有意识到第二次签入将被转换为第二个构建已映射到其工作空间中的路径.因此，第一次签入不是导致CI构建启动的开始，而是第二次签入.

This issue turned out to be a mistake on my end. After my build succeeds I have a couple of automatic check-ins submitted. The first one included ***NO_CI*** and the second didn't. I had not realized the second check-in was being made into a path that a second build had mapped in it's workspace. Thus, the first check-in wasn't causing the CI build to kick off, it was the second check-in.

这篇关于为什么*** NO_CI ***仍会导致连续的内嵌构建?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！