Following on from http://devnet.jetbrains.net/post!reply.jspa?thread=280316 but with slight different intent ...
We have recently ported from TFS Team Build to TeamCity (v6.5.1)
Team Build supports gated checkins => submit a build and if it passes the submit the code AND don't trigger another build. This is nice => the code only gets submitted if it passes and the code only builds once on the build server. The gated checkin shows up on the build's dashboard as you would expect.
TeamCity supports Pre-tested commit => submit a private build, if the private passes then submit the code. This is all great but since the pre-tested commit was a private build, no one else can see it. (The code is committed to TFS, however the private build that checked in the code does not show up on anyone else’s build dash board). When you look at the build dashboard, you get the impression that no one has checked in and therrefore you can't tie a build to a checkin since you cannot see other people's private builds. To overcome this we have set up a normal VCS build trigger that triggers a normal build at the point the pre-tested build commits.
My issue is that
this is a waste of build server resource (disk IO, memory and available build agents). We are having to run the build twice to get the build to show up on the build dashboard.
a private build should somehow become public if it commits => it has moved the code base so the team needs visibility.
Has there been any progression on this? Is there another way to do this?