Magic TFS CheckIn comment to keep a CI build from being kicked off

Buck Hodges - TFS 2008: How to check in without triggering a build when using continuous integration

“If part of your build process is to check in a file, such as an updated version file, you wouldn't want that checkin to kick off another build.  You'd be stuck in an infinite loop.

To prevent that problem, simply put the string ***NO_CI*** in the checkin comment.  The code that examines a changeset to determine whether to kick off a new build will skip any changeset with that string in the comment.

[Update 07/02/2008]  If you are making a checkin as part of the build process, you can use $(NoCICheckinComment).  That property is set at run time when the build agent starts msbuild.  I had forgotten about it until a reader pointed this out.” [GD: Post Leached in Full]

***NO_CI***

Cool. I can use that. There’s times when we check in some associated/tangential resources where it’s just overkill (and pointless) to have a CI build kick off. Having the build go isn’t “bad” but just feels kind of wasteful. Yet not enough to spend a bit of time to tweak the build process. Having this magic comment in my tool belt will be nice…

I wonder what over magic CheckIn comments there are?  :P

(via Dave Lloyd’s 2 Cents - No CI Build on Check-in)