I have TeamCity 4.5.5 Enterprise setup and a Subversion 1.4 server setup. Up until Friday (3 days ago), all my configurations were triggering from Subversion commits. About halfway through the day, TC stopped triggering all together. I've looked at the teamcity-vcs.log file and see that it still queries the Subversion server and sees there are changes. I look in the teamcity-server.log and there are no warnings or errors. If I look at the "Projects" page, the configurations don't even show a "Pending (x)". None of the affected configurations are loaded into the build queue and all the agents are idle. Each configuration has "Enable triggering when files are checked into VCS" checked under "Build Triggering". There are no additional rules in the "Trigger Patterns" box. All configurations are attached to a single VCS Root. The rule in the "Version control settings" are set to look something like this: +:./projectA=>projectA. That is how they are separated out.
The only thing I can think of that I did that day that I haven't done every day was remove some items from the build queue (via the "Remove" option).
At this point, I can manually hit Run... and the configuration will load into the build queue along with all its dependencies and build all the way through. But I have to manually run it and it shows "No Changes" even though there were. It does still track the Subversion revision number. Any help would be much appreciated! Thanks.