A gated check-in will create a change-set whose name is ended with ***NO_CI***? What is that NO_CI stand for? I can just think of "no check in errors" but it doesn't make sense.
It stands for No Continuous Integration.
Since the check-in is gated, the existing code, plus this check-in, will be built separately and only allowed onwards if the build is successful. So when the gating process actually submits it to source control, there wouldn't be any point for that check-in to cause another (continuous integration) build to occur, since at that point thechangeset is 'known good'.
So this suffix is an instruction to the continuous integration system to the effect of: "When this changeset actually gets committed 'for real', don't automatically fire a continuous integration build on account of it".
See eg here for more info.
NO_CI on a check in indicates "No Continuous Integration" i.e. "please don't start a CI build because of this check in".
This means that there will be no CI build triggered after this check-in. You will have to modify your XAML file so that the the CI build is triggered after the gated check-in activity is done.
Please refer to the following link for more information on how to customize the XAML file.
http://donovanbrown.com/post/How-to-have-CI-builds-run-after-a-Gated-Build.aspx
来源：https://stackoverflow.com/questions/3829305/what-does-no-ci-stand-for