Combining “Gated Checkin” and “Continuious Integration” Builds in Team Foundation Server

Question

this Question moved to how to prevent an Gated Check-In to put the Keyword ***NO_CI*** in the Comment

where I put the Question in more detail with my gained knowledge

For ensuring Code Quality and Unit Testing I habe established a Gated Check-In Build in my Project.

Also there is another Build Definition to be triggered by Check-In (Continuous Integration Build), which I want to have build after Check-In.

My expectation was, that The Gated Check in was executed and after successful Build and Commit (by the Build Service User) the other Build is Triggered.

But this is not the Case.

Does any one have an Idea how i get this working, that the Continuous Integration Builds are also triggered by Check-In from the Build Service

Answer 1

In general, it is expected that after a Gated-Build happens & succeeds - nothing else happens after that automatically.
TFS goes to the extend of actually placing a trailer in the commit comments, the infamous ***NO_CI*** that actually tells TFS not to trigger a CI-build after this specific commit.
Check here and here for further descriptions on how it works.

In fact, if you look at this answer, you might find a way to get what you 're after: what @dkpatt did wrong, might be your solution.

Answer 2

How to remove the NO_CI from a build--

1. Open the build template (e.g. DefaultTemplate) in WorkFlow.

2. Search (Current Document/Current Window) for "NoCIOption".

3. The Container should be labeled "GetWorkspace" of type SyncWorkspace.

4. Open Properties (F4).

5. Set the value of NoCIOption to False.

6. Save the build template.