I have recently rolled out the Professional version of TeamCity to one of our on-site development teams, to evaluate how we can benefit from this type of software (we had previously tried CruiseControl.NET but had a number of issues that were not scheduled to be fixed any time soon, so opted to go down a more commercial route, with the general idea of upgrading to the enterprise version of TeamCity if it turns out to be suited to our needs). Our main interest with TeamCity (at this moment in time at least) is to make sure a number of our projects stay in a buildable state across all platforms (currently we support six platforms ). We have three main projects that are being monitored, and we have them setup to be built in both Debug and Release. Two of the projects are mainly based around Visual Studio (using integration to compile for the various platforms) and one of the projects is purely a makefile based project across all platforms. This works in as far as TeamCity will build the relevant projects when changes are committed in to our SVN repositories, and under the right circumstance it'll email users when they break the build, however we appear to have a couple of problems (which from what I can make out are caused by the same issue)....
In our build logs we do not get any messages being reported as 'Important Messages' other than "Unable to cleanup build temporary directory" which is just a warning (as far as I can tell). Ideally we'd like a way to be able to put all our errors on to this page (to make it easier for users to see what the problems are with a given build). All of our builds are done via the 'Command Line' build runner, which basically just calls a batch file that performs all necessary steps to make the build for the various platforms - even the Visual Studio based builds are done in this manner for we have a number of environment variables that are setup (per project) which act as global defines across the solution being built. I have done my best with the documentation and have tried various different combinations, but I am unable to make any of out output appear in this 'Important Messages' window - is there something I have missed? I'd be completely happy with having my own parser which gets all the stdout/stderr from the build process and spits it out in a manner that TeamCity can understand.
Secondly, (hopefully related to the above point), all users are setup to receive an emails, when the build fails, but only for builds in which they have committed to. However, from the documentation is sounds like it'll only email the first user that breaks the build if it detects that the same error has caused the build to break subsequently. So we get in to the state where someone breaks the build, then someone else commits something which also breaks the build, but only the first person gets the email, so they fix what they have broken, the build remains in a broken state, but no one is any the wiser. So my question/hope is that the logic to know 'if the same error has occurred' is based on if the same 'Important messages' are generated for successive builds? If that is the case then my assumption would be if there is some way we can generate meaningful 'Important messages', we should also solve this issue, as the second person to break the build would have generated different error messages.
Any information you can give regarding the above would be appreciated (e.g. is it already possible to fix the above problems, if not is there any likely hood that the above will be added in any future releases, if so what sort of time frame would we be looking at).