TeamCity - My Go-To Build system
Updated April 14, 2017

TeamCity - My Go-To Build system

Christopher Belanger | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with TeamCity

I set up TeamCity for our core product continuous integration. For both the main product and the core libraries it is used to compile on check in, build and deploy on pull requests, and to run the unit and functional tests. No code goes into the develop or main branches without passing through this process.
  • Ease of configuration. Some build systems are difficult to get started on. TeamCity can be up and running quickly.
  • Cross platform. TeamCity runs on most configurations, and a master can configure agents of other OS types, so it can build nearly anything.
  • Price. It's free for limited use, so you don't need to pay until you ramp up and are using it a lot.
  • The upgrade process could be smoother. Moving from one major version to another involves jumping onto all your servers and often causes some pain.
  • Log formatting could be a little clearer, though that is true for almost all build systems.
  • Higher code quality - less bugs made it into production.
  • Easier deployments - no manual steps to get a build onto development and staging environments
TeamCity is the best combination of price and full features. It has a good web UI and doesn't need a lot of manual configuration files, but it still is incredibly extensible and can do just about any build or release task you set it at. If it can't do it, the odds are it has a plugin that can.
Any time you are pushing code, you should be building continuously. TeamCity, like all JetBrains products, is well designed, well supported, and easy to use. I've found no other system that works as well cross-platform. If you don't have CI, you need it and should look at TeamCity.