• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

TeamCity and Visual Studio Team System

 
Ranch Hand
Posts: 77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Kirill,

Can you give a bit of introductory explanation about the relationship between Visual Studio Team System and TeamCity? I haven't dug into either product yet, but as far I hear, Team System is targeted at much larger teams and includes requirements and configuration management and more (and is correspondingly more expensive) than TeamCity.

Does Team System make TeamCity unnecessary, or does it make sense to use the two products together? If it does, are there any plans to support Team Foundation Configuration Management in TeamCity?

Finally, can you offer a guideline as to the size of teams TeamCity works best for?
 
author
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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 ]
 
Mogens Nidding
Ranch Hand
Posts: 77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for your reply - it was very clear.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic