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

18 Reviews

TeamCity packs a mean punch for teams both big and small.

Rating: 10 out of 10

Incentivized

May 20, 2023

Use Cases and Deployment Scope

TeamCity is our primary build, test, and deploy automation tool. It is the key orchestration piece for the SDLC of more than 12 software products. TeamCity allows us to automate a number of tasks to ensure repeatable results and allows team members to spend more time developing rather than running through the manual work of testing and deploying our software solutions.

Pros

build automation.
Deployment automation.
unit test automation.
dependency chaining.
branch management.

Cons

The UI is getting a bit dated but has taken on a serious overhaul in recent builds.
Build configurations as code uses a push/pull mechanism which feels a bit clunky to use.

Likelihood to Recommend

TeamCity is very quick and straightforward to get up and running. A new server and a handful of agents could be brought online in easily under an hour. The professional tier is completely free, full-featured, and offers a huge amount of growth potential. TeamCity does exceptionally well in a small-scale business or enterprise setting.

Verified User

Manager in Information Technology (501-1000 employees)

Vetted Review

8 years of experience

TeamCity, a must for every team

Rating: 10 out of 10

Incentivized

August 16, 2021

Use Cases and Deployment Scope

TeamCity is used across all the development, test and DevOps departments across the company. It's integrated with every GitLab project to provide efficient continuous deployment respecting the priorities of the different projects' builds and the availability of the nodes which are multiple racks. It has been an excellent decision to purchase such a tool.

Pros

User interface
CD
Pipeline

Cons

Updates
Customer service

Likelihood to Recommend

TeamCity is well suited for small teams with several machines as it may become unstable for large projects.

BENAOUN Mahdi

Software Developer in Engineering at Primatec Engineering (501-1000 employees)

Vetted Review

4 years of experience

View profile

TeamCity Delivers

Rating: 9 out of 10

Incentivized

August 13, 2021

Use Cases and Deployment Scope

We make use of TeamCity to build and deploy our code from our git repositories to our various environments - development, test, staging, and production. We have incorporated comprehensive tests into the process as well, making TeamCity the backbone of our CI/CD pipeline that has strengthened our ability to deliver features.

Pros

The ability to have different build processes and monitoring per branch/environment
Run tests as part of the CI/CD pipeline
Status monitoring across multiple projects with build histories

Cons

When it is time to upgrade versions it is a cumbersome and time consuming process
Some of the reporting could be better, no real visualizations of pipelines, histories, etc.

Likelihood to Recommend

TeamCity is well suiting for building and maintaining CI/CD pipelines across multiple branches and environments where each one can have unique build processes and steps. It is straightforward to incorporate tests into the process as well. Generally speaking, it performs well and scales with the business. If you are working with a simple, single project in one environment though you might want to look elsewhere as I think TeamCity might be overkill for your needs.

Verified User

C-Level Executive in Information Technology (11-50 employees)

Vetted Review

4 years of experience

It gives you exactly what is advertised

Rating: 7 out of 10

Incentivized

August 12, 2021

Use Cases and Deployment Scope

The organization is rather small, so it is used by the whole organization, for all the projects we are working on. We are using it to perform tasks of continuous integration and continuous deployment to several environments including test, acceptance and production.
We are also running all our automated unit tests using TeamCity.

Pros

continuos integration
continuos deployment
running tests
highly configurable
fast when using several workers

Cons

the UI can be improved

Likelihood to Recommend

If you are going to host TeamCity in your own server, you will find that it works remarkably well

Verified User

Engineer in Information Technology (11-50 employees)

Vetted Review

9 years of experience

One-stop solution for all build problems in massive organizations.

Rating: 9 out of 10

Incentivized

August 11, 2021

Use Cases and Deployment Scope

TeamCity is being used across my company. We have integrated TeamCity with the CI/CD pipeline. This is solving number of problems which occur if we do not have CI/CD in place. Configuring node servers to build the projects is easy. We can easily configure the properties while building the specific branch. Can easily build multiple feature/develop/release branches at once. It gives all build related information at one place, so can troubleshoot problem in build easily. Basic implementation of application is easy.

Pros

Selection of build server for specific build
We can add configurable properties
One stop solution to create deployable package
Initial and basic setup is easy

Cons

It is not plug and play thing
Need more specific configurations for smaller projects as well
Online help is less available
Basic implementation is easy but I think feature add on can be complex as it involve some language knowledge as well.

Likelihood to Recommend

Well suited :
1. Big organizations where we need central control on builds
2. Apply rules and regulations is central
3. Yet it can be configurable on every build
4. Add different supportive tools of development to find bugs, vulnerabilities.

Not Suited :
1. Small Organizations where no more regulation needed.
2. When no addition of supportive tools required we can end up writing complex config for simple solutions
3. For Start-ups it is not suitable as require specific experienced developer to handle it.

Verified User

Engineer in Research & Development (10,001+ employees)

Vetted Review

2 years of experience

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 (1-10 employees)

Vetted Review

3 years of experience

TeamCity above all else

Rating: 9 out of 10

Incentivized

April 11, 2019

Use Cases and Deployment Scope

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.

Pros

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.

Cons

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.

Likelihood to Recommend

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.

Verified User

Engineer in Information Technology (10,001+ employees)

Vetted Review

2 years of experience

TeamCity is the ideal tool for agile teams using continuous integration

Rating: 8 out of 10

Incentivized

November 30, 2018

Use Cases and Deployment Scope

TeamCity was used by the technology department of the organization, especially by the web development team.

We used TeamCity to test and release code from our development environment to our production environment. Our web developers worked under an agile project management system and used continuous integration. In this system, TeamCity allowed us to integrate our git repository with our ticketing system, as well as help us quality assure and properly release clean code to production.

Pros

TeamCity provides a great integration with git, especially Bitbucket.
When a new code release (build) fails TeamCity has a great tool for investigation and troubleshooting.
TeamCity provides a user-friendly interface. While some technical knowledge is required to use TeamCity, the design helps simply things.

Cons

Upgrading TeamCity is a long and manual process.
Java skills are needed to fully utilize TeamCity, although they are not necessary for basic or medium-level use.

Likelihood to Recommend

TeamCity is well suited for an organization using continuous integration, meaning you release code to production often, and an agile project management system. There are free versions available for small teams and enterprise versions available for large teams with many different builds.

TeamCity is probably overkill for basic e-commerce or blog website builds that do not require much development after the initial launch.

Jason Kelly

Data and Analytics Manager in Information Technology at American Institute for Economic Research (11-50 employees)

Vetted Review

3 years of experience

View profile

My experience with TeamCity

Rating: 8 out of 10

Incentivized

August 3, 2018

Use Cases and Deployment Scope

TeamCity is the go-to tool to getting the Builds and Deployments packages for a variety of platforms like .NET, Java and JS etc. It is being used by the whole organization. It unifies the build and deployments needs of all the diverse projects to a single platform and solves the build and release issues previously we faced and reduces the time to go to Prod.

Pros

First and foremost is the ease of use
Very good support for extending , plugging and scripting support to customize your needs
Lightweight and accessible by browser.

Cons

The Debug log is quite verbose and could be made more intuitive for troubleshooting build errors
I would recommend improving it by some kind of integration with platforms like StackOverflow to aid developers and further improve the turnaround time for setting up successful builds
There is still scope for improvement for build integration with projects in AWS and Azure cloud platforms.

Likelihood to Recommend

It is vary valuable to integrate the traditional .NET , JS, Java projects because of the maturity and the features the platform offers. There's a ton of options to extend the build and deployment process because of the support for scripting it provides. The learning curve is quite easy and the product is intuitive and very natural to understand.

Ramendra Sahu

Sr. Integration Developer / DevOps Engineer in Information Technology at NRECA (51-200 employees)

Vetted Review

3 years of experience

View profile

TeamCity 7 Years On!

Rating: 8 out of 10

Incentivized

May 25, 2018

Use Cases and Deployment Scope

Our company has two products. 1 of which, TeamCity is the critical tool for development and for both products, it's the critical tool for automation testing. In all cases, both development and product support use it. It's the tool which pulls together the 300+ components that make up our current SaaS-based product and the tool which schedules, executes and produces reports for all our type of automation testing (behavioral, backward compatibility, performance, security, and load).

Pros

A very friendly UI with good drill-down and "Pro" capabilities compared to all other CI systems
A good reporting system that allows all our different types of automation tests to produce output for
Fantastically simple to setup and configure

Cons

The biggest and only issue we have is the lack of a SaaS-based TeamCity solution. Currently, we have to host and maintain 1 big TeamCity server and up to 15 build agents to build our 1500+ builds

Likelihood to Recommend

If requiring a CI system and you have VMs available to host it yourself, TeamCity is a great choice.

Simon Hurley

Development Manager in Research & Development at Elateral (51-200 employees)

Vetted Review

7 years of experience

View profile

Loading Reviews List....