问题
This Question is related to my Question Combining “Gated Checkin” and “Continuious Integration” Builds in Team Foundation Server I Posted this Morning
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 discribed 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 answereed but found no real clue.
I grateful for any help.
回答1:
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.
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.
回答2:
vNext Builds - preventing the ***NO_CI***
For vNext builds, check the "Run continuous integration triggers for committed changes" option on the Triggers tab for a build.
See the section "Option to run CI builds" in this reference:: https://docs.microsoft.com/en-us/vsts/build-release/concepts/definitions/build/triggers#gated
来源：https://stackoverflow.com/questions/10106023/how-to-prevent-an-gated-check-in-to-put-the-keyword-no-ci-in-the-comment