After updating our Teamcity server instance from 9.1.1 to 9.1.3, we have noticed that our git vcs triggers seem to be getting ignored and builds that should not trigger are triggering, slamming all of our agents and causing long wait times for critical builds. Note: this may have been occuring since 9.0.2. but i am unable to verify. Is this something that we possibly have setup wrong, or could it be a bug with the software
- 4 build servers with 8 quad cpu's and 128 gigs of ram each and lots of hard drive space
- TeamCity Enterprise 9.1.3 (build 37176)
- 18 agents running as windows services spread across the servers
- VCS are all git (using internal gitlab server we host)
- Each build server has MySysGit 1.9.5 installed and we are using teamcity's built in git vcs system (jgit)
Here is a simpliefied version a build configuration setup. We have a large git repo named cw. Inside that repo there are many folders of different projects. In the client build configuration, it builds a folder called clientstaging. We have all of these build configurations based off templates so that they can be reused.
The git vcs trigger in this example is +:ClientStaging/**
However, if you look at recent builds for this build configuration, you can see that it is triggering when no files in that directory are commited, therefore not matching the trigger.
And the proof git is triggering that build:
To be thorough, here are the vcs settins from the template:
I cannot tell if this is a seutp issue or an actual bug with the system, as it worked fine for the last 6 months until one of the lataest version updates. I searched the forum as well as youtrack and wasnt able to find anything on this. Thanks in advance for the help!
Message was edited by: Matthew Sutterlin