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

查看:13
本文介绍了Tfs 2010 构建:持续集成和门控签入在一起?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经在我的 Tfs2010 实例上运行了一个 CI 构建,但我希望也运行一个门控签入构建.但是,我希望这两个构建运行的方式之间存在细微的差异.具体来说,我希望 Gated checkin 在失败时不产生错误工作项,不在构建时关联变更集和工作项,不将构建移动到 drop ,并且不维护以前的构建.由于由门控签入启动的构建是未提交的更改,因此这些步骤对我来说似乎没有必要,但我绝对希望 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.

不幸的是,在我的变更集被 Gated Checkin 构建提交后,这个 NO_CI 的东西会出现在我的变更集中,并且 CI 构建永远不会被触发.我发现 这个帖子 这似乎表明我的 DefaultTemplate.xaml 应该在某处有一个获取活动"NO_CIOption 参数;但是配置文件中的任何内容似乎都没有表明任何内容.两个字符串都不存在,我在 msdn 库中找不到任何参考文档.

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 了解如何执行此操作.

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

这篇关于Tfs 2010 构建:持续集成和门控签入在一起?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆