Tfs 2010 Build：持续集成和门控在一起？ [英] Tfs 2010 Build: Continuous Integration and Gated Check-In together?

问题描述

我已经在我的Tfs2010实例上运行了一个CI构建，但是我想要一个Gated checkin构建运行。然而，我想让这两个构建运行的方式之间有微妙的差异。具体来说，我希望Gated checkin不会在失败时产生错误工作项，而不是在编译时关联变更集和工作项，不要将构建移动到drop，而不维护以前的构建。由于Gated checkins发起的构建是未提交的更改，这些步骤对我来说似乎没有必要，但我肯定希望CI构建执行这些函数。

I already have a CI build running on my Tfs2010 instance, but I'd like to get a Gated checkin build running as well. There are subtle differences between the ways I would like these two builds would run, however. Specifically, I'd like the Gated checkin to not produce bug workitems on failure, not associate changesets and workitems on build, not move builds to the drop, and not maintain previous builds. Since builds initiated by Gated checkins are uncommitted changes, these steps seem unnecessary to me, but I would definitely like the CI build to perform these functions.

不幸的是， strong> * NO_CI * 在Gated Checkin构建提交后出现在我的更改集上的事件，并且不会触发CI构建。我发现此主题似乎表明我的DefaultTemplate.xaml应该有一个Get ActivityNO_CIOption参数在某处;然而在配置文件中没有什么似乎表明任何类型。

Unfortunately, there's this *NO_CI* thing that appears on my changesets after they're committed by the Gated Checkin build, and the CI build is never triggered. I found this thread that seemed to indicate that my DefaultTemplate.xaml should have a "Get Activity" NO_CIOption parameter in there somewhere; however nothing in the configuration file seems to indicate anything of the sort. Neither string is present, and I can't find any reference documentation in the msdn library.

事实上，在msdn库中有页面，似乎链接到我想要的页面，但是链接实际上会有一个错位，重复链接到控制构建系统放置二进制文件的位置。你可以直接在它下面看到完全相同的链接。

In fact, in the msdn library, there's a page that seems to link to the page I want, however where the link would actually be there's a misplaced, duplicate link to "Control where the build system places your binaries." You can see the identical link directly below it.

无论如何：在构建模板文件中使用NO_CIOption参数是什么？它放在哪里？以前没有人想过这样做吗？

Anyhow: how is the NO_CIOption parameter used in the build template files? Where is it placed? Has no anyone else ever wanted to do this before?

注意：在SO和MSDN论坛之间交叉发帖是不好的做法吗？

Side note: is it bad practice to cross-post between SO and the MSDN forums?

推荐答案

为了跟进，在查看Xaml并使用Build二进制文件中的反射器之后，我在SyncWorkspace操作中发现了NoCIOption属性。将此设置为false似乎允许CI构建在选通检入后触发，以及删除稍微不美观的 * NO_CI * 签入注释附录。

To follow up on this, after looking through the Xaml and using reflector on the Build binaries, I found the NoCIOption property on the SyncWorkspace action. Setting this to false seems to have allowed CI builds to trigger after gated checkins, as well as removing the somewhat unsightly *NO_CI* checkin comment appendix.

请参阅 http://donovanbrown.com/post /How-to-have-CI-builds-run-after-a-Gated-Build.aspx ，了解如何执行此操作。

See http://donovanbrown.com/post/How-to-have-CI-builds-run-after-a-Gated-Build.aspx for information on how to do this.

这篇关于Tfs 2010 Build：持续集成和门控在一起？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！