TeamCity Reviews & Insights

Score7.4 out of 10

60 Reviews and Ratings

Community insights

TrustRadius Insights for TeamCity are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Reliable Performance: Many users have praised the product for its reliable performance. Several reviewers have stated that the product consistently meets their expectations and performs well without any issues.

User-friendly Interface: A significant number of customers have appreciated the user-friendly interface of the product. Numerous users mentioned that the interface is intuitive and easy to navigate, making it simple for them to use and understand all its features.

Great Customer Support: Several reviewers have expressed their satisfaction with the excellent customer support provided by the company. Users have reported positive experiences while seeking assistance from customer support representatives who were helpful, knowledgeable, and prompt in resolving their queries or concerns.

TeamCity Reviews

2 Reviews

Engineering

TeamCity is an important part of our product pipeline

Rating: 8 out of 10

Incentivized

June 29, 2019

Use Cases and Deployment Scope

We use TeamCity on a self-hosted instance to build our ASP.NET projects, .NET desktop projects, and Angular projects. We use it to automatically build these various projects from our git repos and then execute deployment scripts via Octopus Deploy. We also run unit tests on each build and tie in build and test status to our code review tool, Upsource. TeamCity is part of our end-to-end pipeline that allows us to get quality changes out the door quickly and react to production issues quickly.

Pros

See build status across many projects.
It monitors multiple branches with different build processes for each.
It's a useful unit test runner with test history and identification of flaky or problematic tests.

Cons

Reading build output logs can be a pain at times, as they aren't really parsed; just long lines of output.
When you have multiple projects and branches, determining what is currently building, what is pending, and what has failed can be difficult.

Likelihood to Recommend

TeamCity scales well for small teams. We run it on a low-cost instance with several other tools, and it performs well. It has some pretty straight forward build configurations, but can be expanded with scripts and various build settings. It might be a bit overkill for a single, small project, however.

Anthony Aziz

Senior Software Engineer in Engineering at Full Circle TMS (Computer Software, 1-10 employees)

Vetted Review

3 years of experience

Team City: Flexible, Distributed, Customizable build systems

Rating: 9 out of 10

Incentivized

May 16, 2018

Use Cases and Deployment Scope

TC is used across our organization to do builds for all our apps and services. We started using it to replace our custom build and deploy system because we needed something more flexible and customizable, and something that did not need a fully dedicated support team.

Pros

Fully customizable build process. Each step of the build process can be parameterized and customized to address specific needs of particular applications. This allowed us to easily convert from a custom VM-based environment to our current Docker-based environment.
Manages large numbers of build agents seamlessly. This allows us to run multiple builds on many different applications in a most efficient manner.
Build steps can be managed in an arbitrary manner, allowing some parts of the process to proceed in parallel while restricting others to depend on completion of all relevant steps.

Cons

The customization is still fairly complex and is best managed by a dev support team. There is great flexibility, but with flexibility comes responsibility. It isn't always obvious to a developer how to make simple customizations.
Sometimes the process for dealing with errors in the process isn't obvious. Some paths to rerunning steps redo dependencies unnecessarily while other paths that don't are less obvious.

Likelihood to Recommend

TC is great when you have a relatively straightforward sequence of build steps. It allows you to vary the set of build steps by application, and control the dependencies within the build steps.

For our needs, I haven't found any scenarios where TC doesn't provide what we need.

Larry Reed

Senior Software Engineer in Engineering at Survey Monkey (Internet, 501-1000 employees)

Vetted Review

5 years of experience

View profile