We want to trigger a CI build after a gated checkin because we have two builds in our company. One with a gated checkin for fast building and very important test. The other build is for code analysis and long running tests. Because we don’t want to wait very long on our CI build we have created that QM build. The problem is that the QM isn’t triggered anymore after changing the CI build to a Gated checkin build.
I found a blogpost for TFS 2010. Because TFS 2013 is slightly different, I thought I would give it an update.
This is how to fix it for TFS 2013
- Create an argument called “NoCIOption” of the type boolean with default True.
- Set the metadata information so you understand the argument in your build definition.
- Use the argument in the TFS 2013 build template. You can find the property under “Run on agent” and then “Get sources from Team Foundation Version Control”. Go to the properties window and change the hard coded “True” in the NoCIOption property to the argument you just created.
Now checkin your changes of the teamplate and use (if you don’t already have) the template in your CI build (the one with the gated checkin). Change the new argument to “false”.
Now your second build (our QM) is also triggered again.