Why is ***NO_CI*** still causing a continuous intregration build?

Question

I\'ve recently discovered the \"hidden feature\" of TFS that allows you to prevent a CI build from kicking off if your comment contains ***NO_CI***.

I h

Answer 1

Basically, when a checkin occurs, the AT will intercept and fire an event to notify the build component about the checkin. The build component then takes the appropriate action per the trigger type (continuous integration, rolling build, scheduled build, gated-checkin, etc.) of the affected build definitions.

If your checkin comments do contain the string ***NO_CI***, but the changesets still trigger the CI builds, look at the event log(s) on the AT(s) and see if there is any warning with the message "TF215041: Failed to process changeset n".

If your team uses gated checkin build definition, make sure they didn't choose to disable the ***NO_CI*** comment from the build template to allow a gated checkin changeset to trigger CI.