I had to restart our linux server running TeamCity 2.1.1 (we're looking at upgrading, but not right now), and when TeamCity came up, it seems as if the internal buildId numbering counter has been corrupted. When checking older builds under .BuildServer/system/artifacts/ the buildId numbers are at 12000, but the builds since the reboot are now at 2000, which causes a bunch of strange behaviours:
- First of all, every build builds with a warning icon, stating that "This build is outdated. Click the icon to check the newer build results".
- Upon build completion, the latest builds end up at the end of the build history, which means that I need to "view all history records" to see the latest build.
The build history seems to sort builds only depending on buildId, it doesn't seem to matter that both the build number and the build date are newer.
So the obvious question is; is there a way of manually setting the internal buildId value counter, so that we can change it back to 12000+, thus fixing the problem with new builds ending up at the back of the build history?