如何防止门控签入将关键字 ***NO_CI*** 放在评论中 [英] how to prevent an Gated Check-In to put the Keyword ***NO_CI*** in the Comment

查看:19
本文介绍了如何防止门控签入将关键字 ***NO_CI*** 放在评论中的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

这个问题与我的问题有关结合门控签入"和持续集成"构建Team Foundation Server 我今天早上发帖

This Question is related to my Question Combining "Gated Checkin" and "Continuous Integration" Builds in Team Foundation Server I Posted this Morning

感谢@pantelif,我知道在Gated Checkin Build 构建之后,持续集成构建被阻止作为(在大多数情况下)预期行为被触发.Team Foundation Server 将关键字 ***NO_CI*** 添加到签入注释中以执行此操作.

Thanks to @pantelif I know that after a Gated Checkin Build build Continuous Integration Builds are prevented to be triggered as an (in mostly cases) expected behavior. The Team Foundation Server adds to the Check-In Comment the Keyword ***NO_CI*** to do that.

在问题中,您可以在此处找到 描述有人不小心关闭了添加这个魔法阶段.

In the Question you find here there is described that someone accidentally turned off adding this Magic Phase.

我想要的是触发持续集成构建作为预期行为.所以我想避免将关键字放入我的评论中.

What I want is triggering Continuous Integration Builds as an expected behavior. So I want to avoid that the Keyword to be put into my Comment.

我不知道的是怎么做.上面提到的最初问题得到解答后,我在网上搜索了一段时间,但没有找到真正的线索.

What I do not know, is how to do it. I searched the Web for a while after my initial Question mentioned above was answered but found no real clue.

推荐答案

您可以通过设置 NoCIOption SyncWorkspace 工作流活动的属性设置为 false.此处.

You can disable ***NO_CI*** comment by setting the NoCIOption property of the SyncWorkspace workflow activity to false. A similar question and answer can be found here.

您可以关注此博客 post 为您的构建定义实现一个参数,或者您可以在 Gated CheckIn 构建模板中直接将此属性设置为false".

You can either follow this blog post to implement a parameter for your build definition, or you can directly set this property to 'false' in your Gated CheckIn build template.

这篇关于如何防止门控签入将关键字 ***NO_CI*** 放在评论中的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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