What's pro/cons between TeamCity and Team Build and why choose one instead of the other ?
+2
A:
Pros
- Free (Charging doesn't commence until 20 users)
- Supports multiple platforms (Ruby, Java, .NET)
- Supports multiple source control systems
- Supports multiple build runners (Rake, MSBuild, Nant, Ant)
- Excellent reporting options
Cons
- Requires a Java stack (assuming you're a .NET shop)
- Pros
- Integrated solution with Microsoft dev stack
- Cons
- Requires Team Foundation Server ($$$, though Gold Partners get 25 seats free and most other programmes give 5 seats (but you pay for 6 when you add another))
- Only MSBuild supported
Brett Veenstra
2009-12-05 11:33:33
Are you sure Team City requires a Java stack? I was under the impression it supported Visual Studio.
The Matt
2010-02-03 19:19:06
It does support Visual Studio. It also runs on a Java stack.
Joshua Poehls
2010-03-08 14:18:38
A:
If your environment sports a few other opensource/free tools (SVN etc) and utilities I would tend towards choosing TeamCity. We have found it to be pretty cool and integrates with most other popular tools.
If you are "restricted" to MS stack (like you use VSS for source control) then that's the only really compelling reason to go with Team Build.
Mark Gibaud
2009-12-05 11:48:10
If you're using VSS still, you need to **GET OFF IT**. Choose at least Subversion, possibly Mercurial if your devs can grok it! :)
Brett Veenstra
2009-12-05 15:14:10