SVN build triggering stopped working today on our TeamCity server (6.0.2 build 15857). On the project overview page, the changes show up as a yellow "pending" box next to the Run button - but the build doesn't trigger automatically. If I manually click the Run button, it correctly builds the project with the latest changes - the part that's not working is the automatic triggering.

I turned on debug logging and I'm seeing the following in the teamcity-server.log:

We didn't change the build configuration today. The build configuration has a quiet period of 60 seconds, and the VCS root has a check interval of 60 seconds (using the global setting). So the max delay should be two minutes. Currently it doesn't trigger at all though, even after a few hours.

We did upgrade our SVN server last week... but if that's the cause, I assume the problem would have happened sooner. We upgraded from an SVN 1.4 server running svn:// protocol to a 1.6 server accessed over HTTP. I updated the repository URL in the VCS root, and everything worked fine in TeamCity until today.

But this error is not from the time when changes were checked in - it's at 3AM when no one was working. Maybe there was a temporary problem with the SVN server or the network connection.

Here's an example of the triggering problem:

Our "IMS :: Development - CI Build" build configuration has a VCS root of http://inflection2:81/svn/IA/GUI/V4/src. It's configured to trigger the build on every checkin.

According to our svn logs, someone checked in revision 3928 to the repository at 2011-04-27 16:49:03. All the files checked in were under http://inflection2:81/svn/IA/GUI/V4/src. For example, file http://inflection2:81/svn/IA/GUI/V4/src/Client.Core/ViewModels/RefreshableViewModel.cs was changed.

Yegor suggested stopping the server, backing up the .BuildServer\system\pluginData\customDataStorage directory, and then deleting the directory. (This directory is under c:\users\<username>\ on our installation.) This has solved the problem for us - build triggering works properly now.

This issue showed up again for me today right after I "cleaned" the Oracle database (not a big database guy, I just dropped all the tables and let it rebuild [It should be noted, I am just messing around with TeamCity at this point. I'd never do this for real]). Poking around in the folder described above (\.BuildServer\system\pluginData\customDataStorage) I found a folder that corresponded with the build configuration that was giving me problems (\.BuildServer\system\pluginData\customDataStorage\buildTypes\bt2). Inside of that folder are three files, two with what appear to be randomly generated numerical file names and one that is idmap.properties. The contents of one of the numeric files looked like this:

The 85 appears to be the MODIFICATION_ID of the last change that triggered the build. This number has been reset in the Database so new changes have started with MODIFICATION_ID of 1. Looking at the contents of a similar file in a different buildType folder which is set up exactly like this build configuration, but had not triggered anything yet, I noticed the contents were as follows:

<?xml version="1.0" encoding="UTF-8" ?><map/>

I then edited the file in the original build configuration to match and builds are pushing correctly now.