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

This issue turned out to be a mistake on my end. After my build succeeds I have a couple of automatic check-ins submitted. The first one included ***NO_CI*** and the second didn't. I had not realized the second check-in was being made into a path that a second build had mapped in it's workspace. Thus, the first check-in wasn't causing the CI build to kick off, it was the second check-in.