Hello Mogens,
Thanks for the question.
Team System from Microsoft is a complex solution which targets many aspects of software development, including version control system (VCS), running tests, code
exchange between developers. But (and here TeamCity comes to play) Team System lacks continuous integration support and doesn't provide features like pre-tested commit, when you can ask your build system to run tests with your sources without commiting them to VCS.
Currently we are working on integration between Microsoft Team System and TeamCity. This will allow to run Team System builds on the TeamCity, view build history, navigate through tests and open error stacktraces in Visual Studio (right from web-page with build report), and, most noticeably, run builds with your sources without committing them. This will allow to
test your changes without risk to break the build.
We don't have statistics about the size of the teams TeamCity works for. Here in JetBrains, we have > 70 users registered on the local TeamCity server, 20 build agents which continuously run our builds, and > 50 build configurations of different scale.
In our tests, we tested up to 40 build agents working with a single TeamCity server.
[ December 05, 2006: Message edited by: Kirill Maximov ]
