TeamCity for the Win!
March 31, 2017

TeamCity for the Win!

Tom Paulus | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with TeamCity

We use TeamCity at San Diego State Instructional Technology Services to support our CI (Continuous Integration) and CD (Continuous Deployment) needs to support our Agile DevOps practices we implement for our developers. TeamCity also allows us to integrate with our Issue Tracker (YouTrack) and GitHub to ensure we stay on top of issues, and make sure that all of our production deployments are stable and reliable (thanks to Unit Testing, which is handled automatically by TeamCity on artifact build and deploy).
  • TeamCity (via a Plugin) allows us to deploy directly to our Tomcat Staging Server, and via a different plugin, allows us to interface with our Docker Container to do a Zero Downtime deployment to our production system.
  • TeamCity notifies the committing developer, as well as the project lead, if and when a build fails and for what reason.
  • The User interface of TeamCity is also very intuitive and easy to understand.
  • TeamCity's base plan is somewhat limited in regard to the number of projects, specifically build configurations, that you can have.
  • It can take a little bit to get used to the Project Hierarchy structure of TeamCity, however, once understood, it can be extremely powerful for sharing properties and components between projects.
  • TeamCity allows us to automate our Build and Deployment workflow and ensure that committed code works in a standardized build environment.
Team City works great for Java based projects, especially those that work with Gradle. However, TeamCity can work well with any common language. We have found it to be the most powerful and efficient, when TeamCity automatically deals with all of the steps, from automatically picking up a new commit from Version Control, to deploying it to the appropriate system once all the tests and status checks have passed.