TeamCity above all else
Updated May 07, 2019

TeamCity above all else

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

Overall Satisfaction with TeamCity

We use TeamCity as a CI/CD tool for our pre-production and production builds. We've set it up for near full automation use and have set it up with multiple steps for each build. TeamCity is used on a team-by-team basis here at my work. Several surrounding teams in many different departments use it with much success. TeamCity solves the problem of integrating other tools in the CI/CD build process without being too complicated or without too much overhead. Given a corporate firewall can cause great limitations, it's nice to have a tool that's simple to integrate with other tools.
  • Build Automation: easy setup, one-click deployment, reliable use, great documentation/instruction.
  • Tool Integration: great documentation, several existing examples, easy setup.
  • Step tracking: clear pipeline display, easy to locate build logs, clear error messages.
  • Desktop app: TeamCity is browser-based, and some may prefer having a desktop application to view deployments on.
  • Tasteful UI: TeamCity has a simple, non-graphic UI that some may find boring or not as intriguing as some of the other options.
  • TeamCity has greatly improved team efficiency by streamlining our production and pre-production pipelines. We moved to TeamCity after seeing other teams have more success with it than we had with other tools.
  • TeamCity has helped the reliability of our product by easily allowing us to integrate unit testing, as well as full integration testing. This was not possible with other tools given our corporate firewall.
  • TeamCity's ability to include Docker containers in the pipeline steps has been crucial in improving our efficiency and reliability.
I would also like to compare TeamCity against Snap-Ci as well as Concourse. We chose TeamCity over all of these tools because of its ability to be set up easily against a restricting corporate firewall. We needed to integrate unit tests, integration tests, pushes to production, and Docker containers into our CI, but were not able to with the other tools. We found other teams in other departments were having great success with TeamCity so we decided to give it a try and had the same great success. Good documentation is key, and you will definitely find that with TeamCity. There are several extensions or tools available to further modify TeamCity to your needs, but it is an excellent tool out of the box.
TeamCity doesn't slow down when integrating with other tools. It's one of the faster CI tools I've seen. Pages load very quickly, reports are near instant, build logs and the pipeline images are live, and it handles anything we throw at it.
TeamCity is perfect for what it's advertised to do. It's a great pipeline tool that offers several benefits over other tools. What it lacks in a tasteful UI but it makes up for it in functionality, ease of setup, integration with other tools, and one-click operation if set up correctly. Setting up triggers from Github or your favorite source control is very simple, and connecting it to your production deployment is just as easy.