Geek Answers Handbook

TeamCity vs Team Build

What are the pros / cons between TeamCity and Team Build, and why choose one and not the other?

+5
source share
3 answers

Interest Ask. I used both systems to create C # applications.

Teamcity

  • Ease of use
  • Beautiful
  • Easy to install and configure
  • Easy to expand and customize builds
  • It interacts with other systems, such as git, svn, JIRA and many others.

Team foundation build

  • If you already have TFS installed, it's easy to get build start
  • Simple cases like creating a solution are easy to set up
  • Works seamlessly with TFS task management and source control.
  • Bulky and ugly interface

Team (Foundation) Build , TeamCity.

+4

TeamCity

    • ( 20 )
    • (Ruby, Java,.NET)
    • (Rake, MSBuild, Nant, Ant)

    • Java (, .NET)

Team (Foundation) Build

  • Pros
    • Microsoft dev
  • Cons
    • Team Foundation Server ($$$, Gold Partners 25 , 5 ( 6 ))
    • MSBuild
+3

open source/free (SVN ..) , TeamCity. , .

If you are "limited" to the MS stack (for example, using VSS to control the source code), then this is the only truly compelling reason for Team Build.

+1
source

More articles:


All Articles