It's 4:45pm, do you know where your unit tests are? TeamCity does.
March 23, 2017

It's 4:45pm, do you know where your unit tests are? TeamCity does.

Bear Golightly | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with TeamCity

Every single commit to our codebase results in an automatic full build and unit test run, then this code is automatically deployed to a bare-bones environment if it builds and the tests pass.
  • Visual Studio integration is extremely tight.
  • Supports a wide variety of test runners, first-class languages, and source control systems out of the box, and even more with plugins.
  • The configuration system allows our build engineers to reuse build configurations and configuration components, the same way our developers reuse code.
  • The entire thing is built in Java. Not a dealbreaker, but this does mean you need to know Java if you want to create a plugin for something TeamCity doesn't do natively.
  • TeamCity does not seem to have any HA functionality, so no clustering, no active/passive. If your functional CI server dies, your build pipeline dies.
  • The job currently done by TeamCity was previously performed by a full-time employee who did little else, and TeamCity does a better job; this saves the cost of an FTE, at minimum.
  • Logging and reporting allow build issues to be investigated and corrected within minutes, instead of hours, pushing the project along even further.
  • The overall build orchestration and validation provided by TeamCity has removed the angst and anxiety that plagued developers before we implemented TeamCity, which has increased our throughput.
Jenkins and Team Foundation Server (TFS) are both strong products. Compared to Jenkins, TeamCity is much more mature and polished. Though Jenkins is open-source/free, the cost of TeamCity is a drop in the bucket compared to the total cost of even one project we're using it for. TFS was not very mature in 2014 when we started using TeamCity, and we haven't had a need to evaluate in a large project since then - TeamCity has been chewing gum and taking names for 3 glorious years.
TimeForce, Palo Alto Networks VM-200, F5 BIG-IP
If you're developing Java, .NET, or any of the other languages with first-class support in TeamCity (Ruby, maybe?), TeamCity is a great fit for continuous integration; they even have a freemium model if you want to get your beak wet. If you demand an open source solution, you need HA, or you're developing in a non-supported language (Perl, Visual FoxPro, etc), then TeamCity is not a good fit.