We are using TeamCity 3.1.2 accessing StarTeam. From time to time (about once a week) we are seeing some odd behavior with our builds. Sometimes the files that are checked out are not always up to date. We have had numerous occasions when a user will check in two files at the same time. However, when TeamCity checks the files out, one will be up to date but the other will be an older revision. We can manually re-run the build and the exact same behavior occurs. The only way to cure this problem is to delete the source cache in the .BuildServer/system/cache/sources directory. I have actually opened that file (the cache) and seen the incorrect file version in there. Our only workaround at this point is to create a cron job that will delete the entire cache every night before our build kicks off. This does not seem like a viable longterm solution to this problem. Is this a problem anyone else is seeing? If so, has this been addressed in the 4.0 release of TeamCity scheduled to come out soon? I have turned up logging in TeamCity, but I have not seen any odd bahavior such as odd revision times or anything. I would attach the file, but it is several megs in size. Thanks!
Principal Software Engineer
Pitney Bowes Business Insight