结合“门控签到"和“持续集成"在 Team Foundation Server 中构建 [英] Combining "Gated Checkin" and "Continuious Integration" Builds in Team Foundation Server

问题描述

这个问题移到如何防止门控签入将关键字***NO_CI*** 放在评论中

我在哪里用我获得的知识更详细地提出问题

where I put the Question in more detail with my gained knowledge

为了确保代码质量和单元测试，我在我的项目中建立了一个门控检入构建.

For ensuring Code Quality and Unit Testing I habe established a Gated Check-In Build in my Project.

还有另一个构建定义要由签入(持续集成构建)触发，我希望在签入后构建.

Also there is another Build Definition to be triggered by Check-In (Continuous Integration Build), which I want to have build after Check-In.

我的期望是，门控签入被执行，并且在成功构建和提交(由构建服务用户)之后触发另一个构建.

My expectation was, that The Gated Check in was executed and after successful Build and Commit (by the Build Service User) the other Build is Triggered.

但事实并非如此.

有没有人知道我是如何工作的，持续集成构建也是由构建服务的签入触发的

Does any one have an Idea how i get this working, that the Continuous Integration Builds are also triggered by Check-In from the Build Service

推荐答案

一般来说，预期在 Gated-Build 发生之后 &成功 - 之后不会自动发生任何其他事情.
TFS 延伸到在提交注释中实际放置预告片，臭名昭著的 ***NO_CI*** 实际上告诉 TFS 在此特定提交后不要触发 CI 构建.
检查这里和此处 了解有关其工作原理的进一步说明.

事实上，如果您查看 this 答案，您可能会找到一种方法来获得您想要的:@dkpatt 做错了什么，可能是您的解决方案.

In general, it is expected that after a Gated-Build happens & succeeds - nothing else happens after that automatically.
TFS goes to the extend of actually placing a trailer in the commit comments, the infamous ***NO_CI*** that actually tells TFS not to trigger a CI-build after this specific commit.
Check here and here for further descriptions on how it works.

In fact, if you look at this answer, you might find a way to get what you 're after: what @dkpatt did wrong, might be your solution.

这篇关于结合“门控签到"和“持续集成"在 Team Foundation Server 中构建的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！