TeamCity Overview

TeamCity is the #3 ranked solution in our list of top Build Automation tools. It is most often compared to GitLab: TeamCity vs GitLab

What is TeamCity?

TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

Buyer's Guide

Download the Build Automation Buyer's Guide including reviews and more. Updated: June 2021

TeamCity Customers

Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia

TeamCity Video

Filter Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
DevOps Enginee at Local Projects
Real User
Top 5Leaderboard
Scalable and simple to use with lots of very good plug-ins

What is our primary use case?

For my company, we require a CI server that's very flexible. Our bills are simple, almost template-based, however, we need to be able to deploy to almost any platform, basically whatever the customer could end up using, whether it be Windows, Mac, Android, and even mobile or tablets, et cetera. We can do it with this solution. It needs to be simple because right now as I am the only IT person knowledgable of infrastructure on the team. If we need to build a pipeline, it needs to be simple enough that the rest of the team would be able to understand and work with it.

Pros and Cons

  • "TeamCity is very useful due to the fact that it has a strong plug-in system."
  • "If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal."

What other advice do I have?

We're just a customer. We're using the most up to date version of the solution currently. TeamCity is our main continuous integration tool, however, it is deployments that we were looking into improving. With Harness I saw that the deployment process was very polished. And at this point I was wondering if there was any interactivity between the two solutions, or just what would be the benefits of just switching completely to Harness. We're currently researching that now. I'd advise other organizations to do a lot of research before you begin creating anything. The solution needs a lot of…
SG
Lead Engineer at bioMerieux, Inc.
Real User
Top 20
The flexibility of the product allows it to support a seemingly infinite number of build workflows.

What is our primary use case?

Creating build environments for a various range of embedded (C/C++) products with multiple build agent configurations. Empowering the integration team (verification testing) with the ability to test subsystems of applications before launch.

Pros and Cons

  • "I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC."
  • "The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
  • "Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers. I would like them (or partner with someone)​ to provide training classes to help newcomers get things up and running more quickly."

What other advice do I have?

Wish the Tomcat server could magically convert to HTTPS (instead of the apparent default of HTTP). There are published works on using TeamCity (separate works by authors Melymuka and Mahlingam, both on Packt Publishing), however both of these are out of date which makes the initial learning curve more challenging. I invite these publishers to update their work; would gladly purchase updated revision.
Find out what your peers are saying about JetBrains, Jenkins, Atlassian and others in Build Automation. Updated: June 2021.
509,820 professionals have used our research since 2012.
Software Developer at a tech vendor with 51-200 employees
Real User
Stable, a straightforward setup, and easy to configure

What is our primary use case?

We primarily use the solution for application building and testing, continuous integration testing, and continuous delivery.

Pros and Cons

  • "The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications."
  • "If there was more documentation that was easier to locate, it would be helpful for users."

What other advice do I have?

We use the on-premises deployment model. I'd advise others that it's absolutely necessary to use an integration tool that can run integration tests. I'd rate the solution eight out of ten.
Product Categories
Build Automation
Buyer's Guide
Download our free Build Automation Report and find out what your peers are saying about JetBrains, Jenkins, Atlassian, and more!