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)
No comments:
Post a Comment
NOTE: Anonymous Commenting has been turned off for a while... The comment spammers are just killing me...
ALL comments are moderated. I will review every comment before it will appear on the blog.
Your comment WILL NOT APPEAR UNTIL I approve it. This may take some hours...
I reserve, and will use, the right to not approve ANY comment for ANY reason. I will not usually, but if it's off topic, spam (or even close to spam-like), inflammatory, mean, etc, etc, well... then...
Please see my comment policy for more information if you are interested.
Thanks,
Greg
PS. I am proactively moderating comments. Your comment WILL NOT APPEAR UNTIL I approve it. This may take some hours...