--- title: TeamCity Reviews meta_title: 'TeamCity Reviews 2026: Details, Pricing, & Features | G2' meta_description: Filter 90 reviews by the users' company size, role or industry to find out how TeamCity works for a business like yours. aggregate_rating: rating_value: 4.2 review_count: 90 scale: '5' date_modified: '2026-07-18' parent_category: name: CI/CD Tools url: https://www.g2.com/categories/ci-cd-tools --- # TeamCity Reviews **Vendor:** JetBrains **Category:** [Continuous Integration Tools](https://www.g2.com/categories/continuous-integration) **Average Rating:** 4.2/5.0 **Total Reviews:** 90 ## About TeamCity TeamCity by JetBrains is a powerful continuous integration and continuous delivery (CI/CD) solution designed to manage complex build pipelines. Built to support complex systems, high test loads, and strict security, TeamCity facilitates the automation of build, test, and deployment tasks. With TeamCity you can deliver your software in the most cost-optimal way with any tech stack, at any scale. If you need cross-repository build orchestration, scalability and performance of complex software delivery pipelines - TeamCity has you covered.It comes in both on-premises and cloud-based versions, or you can opt for a hybrid setup instead. Key features: •Pipeline optimization: Build caching, artifact reuse, parallel execution, and agent assignment logic to achieve faster builds with less waste. •Scalability: With Teamcity, you can visualize and coordinate multi-step, multi-repo build pipelines with ease. •Test intelligence: TeamCity only runs the tests impacted by a code change using live coverage data collected during builds, making CI processes faster. •Configuration-as-code and Web UI: Use your preferred pipeline setup method between KotlinDSL, UI, or both. •Integrations: TeamCity is ready for real-world setups with a vast number of out of the box integrations for enterprise, hybrid cloud, game dev and so much more. •Combine multiple VCS providers: Connect GitHub, GitLab, Azure, Perforce, Bitbucket, and internal repositories in a single CI setup. TeamCity offers flexible plan and pricing options to fit any project, starting with the free, fully-featured On-premises tier. ## TeamCity Pros & Cons **What users like:** - Users find the **basic features sufficient** for meeting essential testing needs effectively. (1 reviews) - Users find that TeamCity provides **basic features** that sufficiently address some of their testing requirements. (1 reviews) **What users dislike:** - Users find **API limitations** frustrating, encountering issues like unclear branch settings and unreliable build agent behavior. (1 reviews) - Users face **numerous build issues** with TeamCity, causing frustration and inefficiencies in development processes. (1 reviews) - Users struggle with a **confusing interface** in TeamCity, leading to frustration and inefficiency during usage. (1 reviews) - Users report significant **downtime issues** with TeamCity, including offline agents and frustrating UI problems impacting productivity. (1 reviews) - Users face significant **error handling issues** in TeamCity, leading to frustration and disappointing user experience. (1 reviews) - Expensive (1 reviews) - Plugin Issues (1 reviews) - Poor Customer Support (1 reviews) - Poor Interface Design (1 reviews) - Poor UI (1 reviews) ## TeamCity Reviews ### 1. A must have for development team **Rating:** 5.0/5.0 stars **Reviewed by:** Choong Seng C. | Solutions Architect (APAC), Enterprise (> 1000 emp.) **Reviewed Date:** October 30, 2016 **What do you like best about TeamCity?** TeamCity product is very stable and excellent in integration with TFS, it is very well engineered for developer in mind where each activity (build log) are extensively recorded and displayed with ease to navigate UI. **What do you dislike about TeamCity?** Some more refined TFS work item integration would be great, currently it only shows the 1st level of link to the TFS WI as issue list, but that doesn't go well with TFS Scrum template where WI is in hierarchical Feature/User Story/Task. **Recommendations to others considering TeamCity:** To further pair with Octopus Deploy for deployment **What problems is TeamCity solving and how is that benefiting you?** Uses TeamCity for automated Continuous Integration and Deployment for development team. It increases the quality of the deliverable where quality of code is being reported constantly. ### 2. CI done Easily **Rating:** 4.0/5.0 stars **Reviewed by:** Tom P. | Student Assistant, Higher Education, Enterprise (> 1000 emp.) **Reviewed Date:** November 01, 2016 **What do you like best about TeamCity?** TeamCity makes is very easy to implement DevOps in your organization on any scale. **What do you dislike about TeamCity?** While the initial setup can be a little difficult to understand and wrap your head around, it is very easy to setup and configure once you have understood some of the terms that TeamCity uses. **Recommendations to others considering TeamCity:** If you use Git, or other VCS, consider TeamCity for your testing and deployment needs. **What problems is TeamCity solving and how is that benefiting you?** TeamCity has made it possible for us to have a Testing/Staging/Production environment where all the stages are running the correct versions of our codebase. With excellent JUnit integration, as well as Build Status, we know quickly when one of our builds has failed and why. ### 3. Great continuous integration tool for help promote better software development practices. **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Government Administration | Enterprise (> 1000 emp.) **Reviewed Date:** August 29, 2016 **What do you like best about TeamCity?** It is fairly easy to setup and start using right away, easy to setup permissions for different access levels. Helps promote CI and has the ability to track history, notifications on events and monitor repositories for changes. Includes a windows system tray app to monitor in real time any events that you subscribe to. Nice organization of projects and sub-projects with ability to create different builds for each project (Continuous Build vs Ad-hoc deployment builds) **What do you dislike about TeamCity?** Sometimes the Agents stop running for unknown reasons, event logs show nothing out of the ordinary so we need to restart the windows service for things to happen again. There is no notification so it might fail and we will be unaware of it until someone takes notice. **Recommendations to others considering TeamCity:** Microsoft Team Foundation Server Build **What problems is TeamCity solving and how is that benefiting you?** Help developers become away of issues when they check in code and are unaware that their changes have broken the build because they did not run tests locally. It also helps us schedule automated deployments to our integration environment weekly and ah-hoc deployments to our system test environments. ### 4. A Solid All Around Automation Tool **Rating:** 4.0/5.0 stars **Reviewed by:** Christopher B. | Senior Developer, Marketing and Advertising, Small-Business (50 or fewer emp.) **Reviewed Date:** May 19, 2016 **What do you like best about TeamCity?** TeamCity integrates better with .NET tooling than any other automation system out there. From it we can build our pull requests from GitHub, run our unit tests, deploy to integration servers and run our smoke tests. It hooks in well with other JetBrains tools (we use Reharper and DotCover) and logs in with domain credentials, keeping life simple. **What do you dislike about TeamCity?** The configurations are not nearly as simple as they could be. When changing a setting, it is not always clear what is driven from the build master vs the build agent. It would also be much better if the program could update in place on its own, updates are a bit of a process. **What problems is TeamCity solving and how is that benefiting you?** Before TeamCity, we did not have abny way of running our pull requests through a validation process. Now our code is all required to run and be tested on every commit. With the GitHub intergrations, we are even able to enforce that the tests are passing before the code moves forward. Our code is more stable and reliable thanks to TeamCity. ### 5. Easy to setup and use build server **Rating:** 5.0/5.0 stars **Reviewed by:** Giorgi D. | Head of Internal Platform Development Unit, Banking, Enterprise (> 1000 emp.) **Reviewed Date:** October 04, 2016 **What do you like best about TeamCity?** The best thing is that the UI is very user friendly and easy to set up. The functionality is also very flexible and powerful. Also it supports all of the popular version control systems so it can work with any of them. Also the free Pro version comes with enough build configurations to use the system for many different projects. **What do you dislike about TeamCity?** Teamcity has many configuration options and powerful functionality so it can be overwhelming to navigate and understand all the available options. **Recommendations to others considering TeamCity:** I would recommend to start using TeamCity as soon as possible and automate your builds and deployments. **What problems is TeamCity solving and how is that benefiting you?** Teamcity allows us to quickly identify all the failed builds and deploy code to test and live environment without manual work. ### 6. Most feature-complete CI server I've used **Rating:** 4.0/5.0 stars **Reviewed by:** Connor H. | Application Developer, Internet, Small-Business (50 or fewer emp.) **Reviewed Date:** April 22, 2016 **What do you like best about TeamCity?** Once you've got TeamCity running you're just a few clicks away from the most pleasant setup experience around. You can easily extend the capabilities of your server by harnessing community developed plugins that are capable of just about anything, from running simple test suites to building games with the powerful Unity game engine. **What do you dislike about TeamCity?** Compared to the setup of services such as Atlassian Bamboo, Jenkins and Travis CI, TeamCity can be a drag to configure. Whilst it certainly is worth it in the long run it's simply a lengthy inconvenience for those who are tasked with doing it. **Recommendations to others considering TeamCity:** Make sure to take full advantage of the free trial, you should be able to cram as much testing as you need in to ensure it's the right product for you. If you are looking to work with a specific language then you should check out the available plugins before trying it to make sure that said language is actually supported. **What problems is TeamCity solving and how is that benefiting you?** TeamCity is primarily used to automate the periodic execution of various test suites we write for our projects, recently we've decided to take it a step further and have TeamCity deploy built artifacts to our bug finding environment before letting the QA testers have their way. ### 7. TeamCity is awesome you should use it if you're into continous integration **Rating:** 4.0/5.0 stars **Reviewed by:** Arbi A. | Concepteur/Développeur, Telecommunications, Enterprise (> 1000 emp.) **Reviewed Date:** April 20, 2016 **What do you like best about TeamCity?** I previously worked for a software company that develop JEE applications. We had TeamCity for continuous integration and building. What we liked about it was the quality of the tool and even it's not a free one (although you can a limited environment for free package that includes the TeamCity CI server and three build agents) the paid support behind it. But even if it cost money, it's price is still affordable compared to Microsoft products (we had one .Net developer that used Visual Studio). We also liked one neat feature in TeamCity which is the web-based dashboard. It gave us a quick overview of our project status, additional to reporting information that can be convenient for a various kind of users and anyone involved in the project. It also gave us the build progress, ability to get more details with a drill down approach, in addition to historical data on the projects and configurations to keep an eye on changes. **What do you dislike about TeamCity?** May be the fact that it is not an open source project. We, especially in the java ecosystem, used to open source, we use other people work and give back to the community whenever it is possible. **Recommendations to others considering TeamCity:** Give a try to TeamCity and you'll like how cool it is: - TeamCity is extremely easy to setup, configure and use. - TeamCity is deeply integrated with a lot of tools and technologies without need for complicated configurations, - TeamCity is not that expensive compared to any commercial dev tools out there, - TeamCity is secure, **What problems is TeamCity solving and how is that benefiting you?** We used TeamCity for continuous integration of JEE applications, and to keep track on the how development is evolving and regression tests. We also made benefit of the code analysis built-in feature. ### 8. We use this for our CI builds **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** July 14, 2016 **What do you like best about TeamCity?** It provides a good way to setup builds, and run unit tests with github checkins. We have it setup to run unit tests for our mobile apps whenever someone submits a pull request to github. **What do you dislike about TeamCity?** The github integration setup could be easier. It might be nice to just have pre-set check boxes to determine when you want something to be run, instead of using some branch syntax to determine that. **What problems is TeamCity solving and how is that benefiting you?** This helps us build quality products since we are able to run unit tests each time a new commit is made. This helps us know up front if something in the commit is wrong rather than in production. ### 9. Great tool for managing builds and deploys **Rating:** 5.0/5.0 stars **Reviewed by:** Larry R. | Senior Software Engineer, Internet, Mid-Market (51-1000 emp.) **Reviewed Date:** April 26, 2016 **What do you like best about TeamCity?** Totally flexible, but has good functionality out of the box. You can create your own processes and controls. **What do you dislike about TeamCity?** Can sometimes be confusing how to figure out what you can or can't do. **Recommendations to others considering TeamCity:** This tool is not for amateurs, but the amount of up front time you invest it getting it working is well worth it. It is important to understand what you want out of your development processes, and have a clear set of guidelines and process controls before you start. But if you have these, TC will make it possible for you to manage things flexibly and in a distributed manner. **What problems is TeamCity solving and how is that benefiting you?** We are using this for managing builds and deployments. It has allowed us to make significant progress towards our goal of Continuous integration, and has liberated our devops team from the necessity of always being involved in every release at every stage. ### 10. Simply powerful and flexible continuous integration tool **Rating:** 5.0/5.0 stars **Reviewed by:** Kasim T. | Senior UI Engineer, Internet, Small-Business (50 or fewer emp.) **Reviewed Date:** November 08, 2016 **What do you like best about TeamCity?** I like the flexibility to customize the build using command lines. **What do you dislike about TeamCity?** Upgrades might be a pain, would be great if the process is automated instead of manual. **Recommendations to others considering TeamCity:** TeamCity is super easy to setup and get it run within minutes. **What problems is TeamCity solving and how is that benefiting you?** Automation process for tests and continuous deployment. ### 11. The easiest-to-use and most feature-complete CI server you can find **Rating:** 4.0/5.0 stars **Reviewed by:** Jonathan E. | Owner, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** March 29, 2016 **What do you like best about TeamCity?** Once TeamCity is up and running, configuration for projects and builds is a breeze. Community-provided plugins allows us to easily expand functionality (such as the Unity Runner for building Unity projects, or the SFTP Deployment plugin to handle deployments over SFTP). When compared to its alternatives, TeamCity's UI is both functional and aesthetically pleasing. **What do you dislike about TeamCity?** Initial installation/setup was not as smooth as some of the competition, which makes upgrading TeamCity a somewhat cumbersome process. As a result, we rarely upgrade unless a new release fixes a blocking or nuisance issue. Built-in support for various languages is quite lacking. The bulk of our projects' build steps are shell scripts. Building projects using ant or MSBuild is incredibly easy, but for many other languages (for us, mainly Python) the initial setup of your build configuration can be a bit daunting. **Recommendations to others considering TeamCity:** TeamCity's free license should be sufficient for an organization of any size to give the system a try and see if it will meet all business requirements. **What problems is TeamCity solving and how is that benefiting you?** We use TeamCity to perform automated tests and, most recently, automated deployments to our staging environments. By removing the need for us to perform deployments manually, a bulk of our time has been freed up for other tasks. ### 12. As a developer I use team city for building our code libraries. **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Industrial Automation | Enterprise (> 1000 emp.) **Reviewed Date:** August 27, 2016 **What do you like best about TeamCity?** Builds pretty quick and it has many options for connecting to several source control software. I also like the flexibility given with setting up build triggers. **What do you dislike about TeamCity?** The user interface for team city could use an update. **Recommendations to others considering TeamCity:** I recommend this product for automated build/test environment with a continuous integration focus, **What problems is TeamCity solving and how is that benefiting you?** We use team city to build our product code. Our product is split into many libraries with many inter-dependencies. Team city allows us to automatically build our libraries in the correct order whenever we submit source code changes to your source control software. It also allows us to run automated unit tests on individual libraries, as well as smoke tests on our product build. ### 13. Paid continuous integration **Rating:** 0.5/5.0 stars **Reviewed by:** Francesco M. | Owner and BI/Data Architect, Mid-Market (51-1000 emp.) **Reviewed Date:** July 19, 2016 **What do you like best about TeamCity?** Many options, Java based so easy to integrate a Maven project. Coming from Jenkins I found TeamCity annoyingly complicated, even setting it up using docker was not easy. **What do you dislike about TeamCity?** Bad documentation, difficult to find help Googling problems, cumbersome setup. I wanted my Jenkins back as soon as possible **Recommendations to others considering TeamCity:** Check Jenkins before using TeamCity, if Jenkins is enough (probably it will be even more) for your requirements go with it and forget about TeamCity. **What problems is TeamCity solving and how is that benefiting you?** Build and deployment of a web application on different Tomcat server (for development, testing and production) using different Maven profiles. ### 14. Handy tool for Continuous Integration **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Wireless | Mid-Market (51-1000 emp.) **Reviewed Date:** January 29, 2017 **What do you like best about TeamCity?** Heavily reply on TeamCity for Continuous Integration of SourceCode. This product has a great integration with GitHub (including webhooks). Quite a few plugins are available for CodeCoverage, Unit Testing as well as integration with some products like HipChat. **What do you dislike about TeamCity?** This is a great product, and meets my expectations. **Recommendations to others considering TeamCity:** This is a great product for Build Automation and Continuous Integration. Leverage product integrations with GitHub. **What problems is TeamCity solving and how is that benefiting you?** Source Code Continuous Intgration ### 15. An excelent and configurable CI server **Rating:** 5.0/5.0 stars **Reviewed by:** Michael J. | Lead Network Architect & SysOps, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** March 08, 2016 **What do you like best about TeamCity?** TeamCity is a very flexible CI server. It can work with nearly any language or build system, provided the tools are present and can be run in a "headless" manner. Since the build process uses agents that can be installed remotely and on different operating systems, a single TeamCity server can be used for cross-platform development. Build steps are completely configurable and can range from built-in steps (MSBuild, Ant, etc) to scripts, to "meta-runners". It also supports displaying code coverage information, test output and VCS history. **What do you dislike about TeamCity?** The largest problem with TeamCity is that it's very memory-hungry. Expect to devote a server to the service if you're going to use it. It's coded in Java (like nearly all of JetBrains' other tools) on top of the Tomcat servlet engine. It's also just slightly custom enough that running it on a vanilla Tomcat install is very painful. **Recommendations to others considering TeamCity:** There are a lot of CI solutions out there. TeamCity works best when you can self-host the system and have the in-house knowledge to maintain it. It may also be a great value as many services, such as Visual Studio Team Services can get expensive when you have complex and long-running build processes. TeamCity also has a no-cost license level, which is great for trial or usage by small companies. **What problems is TeamCity solving and how is that benefiting you?** With a large, distributed team working on a complex project, it's very important to keep code quality in check. Automating tests and deploying to a QA testing environment helps keep turnaround fast and allows our developers to get quicker feedback on their code. TeamCity gives us confidence that our code will build and run properly. ### 16. TeamCity makes automated build easy. **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** May 20, 2016 **What do you like best about TeamCity?** TeamCity is such an improvement on the old XML-based build systems of the past. It has a user interface that makes the entire build process easier and integrates with all the relevant systems and source control providers and even allows you to use Amazon AWS to utilise the cloud for build agents. **What do you dislike about TeamCity?** It can be somewhat daunting to a beginner but that is really more down to the power that it has and is based on the complexity of building software and all the various dependancies a software build has. There are worse interfaces out there and the help documentaion helps you manage this. **Recommendations to others considering TeamCity:** TeamCity is probably the easiest build server setup i have used and it has all the pieces needed to get the job done and is priced fairly and even has a freemium style pricing so you can kick the tyres on it. **What problems is TeamCity solving and how is that benefiting you?** Build automation via collecting your latest code from source control and all the depandanices needed to procuce the artifacts ready to actually deploy software to various environments. ### 17. Versatile Continuous Integration solution with a LOT of features **Rating:** 4.5/5.0 stars **Reviewed by:** Daniel R. | Independent Software Developer, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** January 25, 2016 **What do you like best about TeamCity?** The flexibility of the platform to fit complicated build scenarios, coupled with the amount of data it can give you, is what drives my love for this product. We have 100's of projects being built across many branches and build agents, and TeamCity makes it relatively easy to manage. It runs our tests, notifies when projects fail to build (before they hit our multi-hour overnight build process!) and it can package up products for use by internal teams. **What do you dislike about TeamCity?** It can be a very complex system, so when something goes wrong, we've had some difficulty tracking down exactly where the problem is. There are a LOT of settings, and each project could potentially have it's own unique set of configuration. Setting up the build agents from scratch is something that takes a while based on our software requirements, a way to spin these up in a more automated fashion would be nice if somehow incorporated into TeamCity. **Recommendations to others considering TeamCity:** TeamCity really shines when you pair it with other products from Jetbrains. It isn't the easiest Continuous Integration system to set up, but by their very nature, few are. Taking the time to set up projects and dependencies from initial implementation, and using templates when possible, will save you a lot of time and headaches down the road. **What problems is TeamCity solving and how is that benefiting you?** TeamCity is used to continuously build projects as developers make changes. It is responsible for running all of the unit tests on each check-in, and triggering any projects that may be downstream in the dependency chain, running tests on those projects as well. This has the primary benefit of being any early warning system to any changes that may impact functionality not only in the project changed, but in other products that make use of that project. This helps ensure our release build process will go smoothly each night, as problems are usually caught early by TeamCity while everyone is still in the office. ### 18. Decent CI/CD Software **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Transportation/Trucking/Railroad | Mid-Market (51-1000 emp.) **Reviewed Date:** April 08, 2016 **What do you like best about TeamCity?** It was very easy to setup. The interface is logically laid out. It supports a number of nice features including automated tests, dependency checks, support for many different code repositories including cvs and svn, and requires only occasional maintenance. **What do you dislike about TeamCity?** It doesn't integrate with our other Atlasssian products as nicely as Bamboo does. Which to be fair is expected as Bamboo is also an Atlasssian product. Builds will typically generate a fair amount of files and artifacts which can quickly consume disk space. The cleanup routines within Teamcity need to be carefully tuned to avoid filling your disks. This can become an onerous task. **Recommendations to others considering TeamCity:** TeamCity is roughly equivalent to Jenkins and Bamboo. With Jenkins it's very extensible but will require more manual configuration and fiddling versus TeamCity and Bamboo which are both polished commercial products. If you are already using Atlasssian products, you'll gain better integration by using Bamboo. If you aren't an Atlasssian shop, then TeamCity offers similar functionality. You'll need to make your decision based on current features, UI, and prices for each. **What problems is TeamCity solving and how is that benefiting you?** We were looking for a good continuous integration, testing, and deployment server ### 19. TeamCity has all the required features for an integration and build tool **Rating:** 4.0/5.0 stars **Reviewed by:** Liam B. | Mobile Developer, Internet, Mid-Market (51-1000 emp.) **Reviewed Date:** January 06, 2016 **What do you like best about TeamCity?** TeamCity is a helpful and intuitive platform for continuous deployment of new builds and releases. It provides a clean user interface and has got easy navigation options. It provides running automated tests in the build process and allows to view the issues along with detailed log information. One of the best features of TeamCity is Publish Artifacts which allows anyone to deploy the code or even build directly in any environment such as development, testing, clone or production. It shows the progress of the build at every step and the number of tests remaining to pass before the build is complete and turns green. It also let you to rerun any of the failed test even after overnight execution of the same. This saves manually doing the execution again the next morning. The overall functionality can be easily understood by going through the provided user guide which is thorough as well as extensive. **What do you dislike about TeamCity?** To setup the build configurations initially, it involves many steps because the process is broken down. There is no option for deploying the application for the source code to be present in a particular build such as my main repository. **Recommendations to others considering TeamCity:** If you are searching for an enterprise build management software, then TeamCity is definitely worth considering. It is also suitable for freelancer developers who have got a limited budget, as TeamCity is free up to certain number of projects. **What problems is TeamCity solving and how is that benefiting you?** After using TeamCity, the process of continuous integration has become more concise and has also reduced the number of build failures. The issues gets highlighted pretty quickly and I am able to replicate issues on a fast track. The best thing I found out was acceptance tests can be made to run after every single commit which provides faster response in the quality test. A lot of time is saved with the automated deployments for scripts, applications and web services. This pipeline process has also reduced the manual errors. ### 20. Using TeamCity has been great so far! **Rating:** 4.5/5.0 stars **Reviewed by:** Peter S. | Software Engineer, Outsourcing/Offshoring, Mid-Market (51-1000 emp.) **Reviewed Date:** December 23, 2015 **What do you like best about TeamCity?** We use Team City as our build server, and it has been great at letting us organize and track all of our builds. We have a 100+ solutions that are being contributed to and being built pretty frequently. We also use TC to kick off unit tests after each build and let us know if there are any failures via email. **What do you dislike about TeamCity?** Setting up a build could be simpler. We use a pretty basic setup - but I feel like I have to jump through hoops to get everything correct. I understand that having options complete multiple steps is important, but maybe these extra steps could be added in at will, not included in ever basic setup. **What problems is TeamCity solving and how is that benefiting you?** I have worked at a few places, and each seemed to have a different solution for a build server. Team City has been the one I have been the most involved with, and also the easiest to use so far. ### 21. CI Solution from JetBrains. Easy to configure and manage. used it extensively for our java projects **Rating:** 4.5/5.0 stars **Reviewed by:** Imran H. | Software Engineer, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** December 10, 2015 **What do you like best about TeamCity?** i was first introduced to teamcity when contributing upstream to mesosphere projects. there i saw that their gating runs very fast and steady and on an environment called teamcity. i was impressed and tried my own on my windows machine. needless to say, the interface , the visibility and ergonomics were brilliant. for instance: Cross-platform builds The fact that it's based on Java does not hinder it's capability to support different build environments. TeamCity supports a large number of tools and languages. Easy installation TeamCity's installation is really simple. It has different installation packages for different operating systems. All that's needed is to download the correct one and run it. **What do you dislike about TeamCity?** Projects and configurations are not kept under VCS TeamCity does not keep projects and configurations under Version Control. This means that deploying older revisions of a project is almost impossible is TeamCity has complete control over the source code and deployment packages. Besides, you probably cannot use this approach with free version of TeamCity, because it does not allow having more than 20 configurations per project. **Recommendations to others considering TeamCity:** please try first, and integrate before releasing out to average users. **What problems is TeamCity solving and how is that benefiting you?** TeamCity provides nice set of feature for building your project and packing result binaries into deployment package. You can use them to get a quick start (of course if you already have some experience with these features). But keep in mind that TeamCity is not a Holy Grail of continuous integration process. Having 100% dependency on TeamCity is not good. There might be a moment when you have to build and package your project without TeamCity. So try to create stand-alone build scripts and use TeamCity only for calling these scripts when certain events occur (new commit, time schedule, user request, etc.). What TeamCity does really well is running automated tests and reporting their status. ### 22. Powerful CI tool **Rating:** 5.0/5.0 stars **Reviewed by:** Viacheslav S. | Software Developer, Internet, Mid-Market (51-1000 emp.) **Reviewed Date:** April 27, 2016 **What do you like best about TeamCity?** Easy install. Easy configuration. No dependencies. Support of NuGet, Powershell, NUnit. Support of various VCS. Ease of scalability via adding more agents. Build Notifications are easily configured and always work fine. Good for small teams and easily extended for big company via licensing. **What do you dislike about TeamCity?** CodeCoverage is not available from the box as for TFS. To support Code Coverage, paid tools are required. No other issues for my development requirements. **What problems is TeamCity solving and how is that benefiting you?** Continuous integration. Continuous testing Complex deployment procedures. ### 23. Best CI out there! **Rating:** 5.0/5.0 stars **Reviewed by:** Joel D. | Cofounder, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** January 14, 2016 **What do you like best about TeamCity?** TeamCity is one of the best Continuous Integration servers out there! When it comes to ease of use it's pretty simple to setup. I wanted to use it for Android builds and once I got my virtual machine up and running and got the team city installer fired up, in the matter of minutes team city was ready. Once I connected it to my Android build environment (SDK, and Java environment) I was building from my GIT repo in no time. **What do you dislike about TeamCity?** So far I havent relly had any major issues with it to dislike anything per say. It's a CI server that caters to a particular audience so if one doesn't like it they can easily just switch to Circle CI or Travis CI. The main issues I was having were mostly Windows related security issues. As windows has several methods that protect certain administrative functions so I had to configure the current account to have these priveleges so that it could trigger builds. **What problems is TeamCity solving and how is that benefiting you?** Team City has allowed me and my team to automate the whole process of building, by allowing us to folow Continuous Integration principles. Now every time we check in to our GIT repo it triggers a build of our Android app. So we are continous improving and doing validation as we build along so we don't have major issues when it's time to deploy to production if we were working on module's seperately. It solves the issue of ease of use where it allows us to focus on the core and does all the behind the scenes work for us by providing an abstraction layer above that via a nice user interface. ### 24. TeamCity is nice and intuitive for build and CI **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Small-Business (50 or fewer emp.) **Reviewed Date:** August 03, 2016 **What do you like best about TeamCity?** Intutive, interface, quick and painless setup, more fun to use than Jenkins. **What do you dislike about TeamCity?** No build configuration export, which is solved in latest version. **Recommendations to others considering TeamCity:** Basically one of the best CI tool ever. **What problems is TeamCity solving and how is that benefiting you?** We use it to build application releases and testing. It solved us a lot of time and efforts. ### 25. I have used TeamCity for 8 years in the companies **Rating:** 4.0/5.0 stars **Reviewed by:** Dave L. | Principal Release Engineer, Information Technology and Services, Mid-Market (51-1000 emp.) **Reviewed Date:** December 18, 2015 **What do you like best about TeamCity?** TeamCity meets the majority of my needs for CI builds. It is flexible and transportable. I have been using it since v0.8 and have seen great features added over the years. I like sub-projects and REST API features that have been added. We get a lot of use out of the Issue Tracker linking to Jira. The custom reports is a useful feature. We like the fine-grained user permissions as our company grows and because we use a TeamCity server in multiple environments. **What do you dislike about TeamCity?** I have made a few feature requests that have not been addressed yet like the ability to reuse certain build failure conditions across multiple build configs. These are fairly minor. There have been some performance issues that occasionally require restarting the TeamCity server. I would like a default VCS user/pwd for our 200+ VCS roots although we do have a workaround for that now. **What problems is TeamCity solving and how is that benefiting you?** We have 2 enterprise servers and 22 total build agents spanning multiple environments. All of our automated builds and deployments as well as most maintenance is done through TeamCity. ### 26. Team City **Rating:** 5.0/5.0 stars **Reviewed by:** Ruslan A. | Senior Software Engineer, Transportation/Trucking/Railroad, Enterprise (> 1000 emp.) **Reviewed Date:** December 18, 2015 **What do you like best about TeamCity?** Nice interface, easy to use. Has enough feature to help with daily tasks, like clone, intellisense, attaching source control, etc. **What do you dislike about TeamCity?** Lack of clear explanation in documentation. If you're new to TeamCity then it may not be easy to get started. One of the best tool for Continuous Integration but not so good for Deployment. Doesn't offer a proper deployment pipeline. **Recommendations to others considering TeamCity:** One of the best tools for CI but lack of proper CD. Also consider Visual Studio Online or how it was renamed recently - Visual Studio Team Service. **What problems is TeamCity solving and how is that benefiting you?** Continuous Integration and Deployment ### 27. Great tool for integrated builds **Rating:** 4.0/5.0 stars **Reviewed by:** Rita D. | Technical Project Manager, Enterprise (> 1000 emp.) **Reviewed Date:** February 12, 2016 **What do you like best about TeamCity?** We use teamcity for integrated builds. It is an excellent tool for automating builds. We use Teamcity because it's easy and even the BA and PM can trigger a build. It makes is easy and convenient for the team to have builds deployed. **What do you dislike about TeamCity?** So far I haven't found anything that I dislike about it. **Recommendations to others considering TeamCity:** Its a great tool for integrated builds **What problems is TeamCity solving and how is that benefiting you?** We use Team City for integrated builds. We like it because not just the developer but even the BA and PM can trigger a build and deploy one when necessary. ### 28. TeamCity - Newforma - Mariellen **Rating:** 3.5/5.0 stars **Reviewed by:** Mariellen P. | Senior Quality Assurance Engineer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** December 10, 2015 **What do you like best about TeamCity?** Well defined workflow. Up and running within minutes. The dashboard is easy to setup and configure your own preferences. Supports many languages and plug-ins. **What do you dislike about TeamCity?** The logging could be more verbose. Sometimes it takes a while to figure out why the build broke and/or the failure isn't really related to the error displayed. **Recommendations to others considering TeamCity:** The dashboard is easy to configure and implement your builds. Not too many "customized" actions taken to get a great product working with our source control and automation scripts. **What problems is TeamCity solving and how is that benefiting you?** Build and automation workflow. Build all the components and implement automation was easy to setup and get running. Again, supports many of the latest technologies. ### 29. Seamless build server for everyone **Rating:** 5.0/5.0 stars **Reviewed by:** Roberto O. | Android Developer, Research, Mid-Market (51-1000 emp.) **Reviewed Date:** December 09, 2015 **What do you like best about TeamCity?** The feature that really stroke me the most is the integration with Gradle: just for that, and for the ease of configuration, I fell in love with this tool! **What do you dislike about TeamCity?** The free tier was somehow limiting and we are not able, as of today, to upgrade to a business plan, so we are stuck with the free version. But hey, there's a free version! **Recommendations to others considering TeamCity:** If you need a single environment for having everything building in one place... you found your solution! **What problems is TeamCity solving and how is that benefiting you?** We wanted a single building environment for all of our apps, from Windows Phone, to iOS, to Android, with the possibility of integrating tests easily. ### 30. The best CI tool **Rating:** 5.0/5.0 stars **Reviewed by:** Roger B. | Engineering Lead, AEM, Marketing and Advertising, Mid-Market (51-1000 emp.) **Reviewed Date:** December 18, 2015 **What do you like best about TeamCity?** I have reviewed a few CI tools, Jenkins, Bamboo, Travis, and Team City. Team City is by far the best CI tool on the market today. I can't say enough good things about this tool. Would recommend it to absolutely anyone looking for a CI tool. **What do you dislike about TeamCity?** There is not a single bad thing I can say about this tool. It is a phenomenal tool. **What problems is TeamCity solving and how is that benefiting you?** Our company needed a CI tool, it was my job to review and select one. Team City won the battle by a long shot. It does everything the other do just more intuitively. ### 31. I love TeamCity **Rating:** 5.0/5.0 stars **Reviewed by:** Oscar H. | QA Developer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** May 28, 2015 **What do you like best about TeamCity?** TeamCity is a java-based CI server package. The TeamCity installation is extremely easy and very quick. I find the TeamCity browser-hosted dashboard absolutely amazing. It is also very simple and easy to get familiar with. It also It provides build progress, drill down detail, and history information on the projects and configurations. **What do you dislike about TeamCity?** Very few dislikes. I guess that every release introduces a few new bugs, which can be annoying. Also, it requires a Java stack (assuming you're a .NET shop). I do not really like the layout and design of TeamCity though, it can sometimes seem a little boring. However, for what it is, it looks quite fine. I just wish that it would include a nicer looking, and maybe even a little more colorful interface, just so that us users can be happy. **Recommendations to others considering TeamCity:** Usually when someone near me asks this type of question, I recommend TeamCity. There are many important .NET tools integrated and included with TeamCity, such as code coverage analysis, several .NET testing frameworks, and static code analysis. **What problems is TeamCity solving and how is that benefiting you?** It provides project status and reporting information suitable for a bread range of users and project stakeholders. There are a lot of good reasons to choose TeamCity. The product is very well documented and there are a lot of examples and tutorials available. Out on the Internet there are many postings ranging from setting up basic CI with TeamCity to advanced topics such as using TeamCity’s built-in NUnit test runner. ### 32. Interface feels a bit old, but delivers what is exepcted **Rating:** 3.0/5.0 stars **Reviewed by:** João M. | Senior Software Developer, Internet, Small-Business (50 or fewer emp.) **Reviewed Date:** January 22, 2016 **What do you like best about TeamCity?** Works as advertised. Pretty Complete. Installation is pretty smooth and works out of the box for most scenarios. **What do you dislike about TeamCity?** Lacks some plugins, and the interface is a bit old. **What problems is TeamCity solving and how is that benefiting you?** Continuous Building a Deploy ### 33. I am a DevOps Manager with over 125 Builds running on TeamCity 9.0.2 with 4 yrs experience. **Rating:** 5.0/5.0 stars **Reviewed by:** Eric H. | Azure Architect, Business Analyst, Pre-Sales Engineer, Microsoft VTSP, Certified MEC Facilitator, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** May 01, 2015 **What do you like best about TeamCity?** TeamCity makes it extraordinarily easy to configure individual builds. By far the best feature is its ability to use parameters for builds, which makes it very easy to create generic build configurations that can be used over and over again. **What do you dislike about TeamCity?** I would really like to be able to build, view and manage builds with a visual pipeline - that feature does not really exist at this time. **Recommendations to others considering TeamCity:** TeamCity is very easy to integrate with SVN, TFS, or GIT. 98% of most configurations can be managed on screen within a discrete set of fields. There are no complex XML or Configuration files to learn, making it easier to get up to speed on than Jenkins. The work flow is well structured and intuitive, making it easier to grasp than Team Foundation Server or Visual Studio Online builds. The product is very stable, with active support and upgrades. The online documentation is outstanding. Response to questions generally comes through the Community or via online ticket response - which can be a problematic if dealing with a serious problem. Best of all - the Professional version is free, with unlimited user licenses and three build server licenses and 25 builds, so getting started is easy and inexpensive. Converting to the Enterprise version for unlimited builds is not expensive. Maintaining upgrade rights is recommended as JetBrains actively updates the product on a semi-quarterly basis with each upgrade adding more functionality. Highly recommended. **What problems is TeamCity solving and how is that benefiting you?** TeamCity is the core of our Agile Development and Continuous Integration process. Every build automatically compiles on TeamCity, sending errors if the independent build fails. TeamCity runs Test Coverage reports for both managed (C#) and unmanaged (JavaScript) code and reports failing tests. All deployments are made from TeamCity where ever possible. This process identifies build and coding issues early in the process - helping prevent last minute deployment issues. ### 34. Development Manager and TeamCity custodian **Rating:** 5.0/5.0 stars **Reviewed by:** Simon H. | Development Manager, Internet, Mid-Market (51-1000 emp.) **Reviewed Date:** May 07, 2015 **What do you like best about TeamCity?** It's simple yet powerful UI plus very useful API. We've now moved away from creating teamcity builds by hand, instead I've created a small app which uses teamcity's api to create builds in a standard manner and without human error. We've even hooked up teamcity to our global package service, which delivers versions of our product to groups of servers hosting our product. We have a large development group of 50+, along with 10+ test engineers, account managers and project managers whom all ahve different views in TeamCity to monitor progress of individual features all the way up to what version of a product distribution has what changes in. **What do you dislike about TeamCity?** Speed. After 4 years of using TeamCity I never seem to get it to operate fast enough for it not to delay your working day. **Recommendations to others considering TeamCity:** Use it. It's a great tool. Very easy to setup and if you need more agent power, you can hook up to azure or amazon ec2 and it can create builds agent vms dynamically when there a build queu that demands it. **What problems is TeamCity solving and how is that benefiting you?** How to compile and version all 300 components in our product in a reliable and organised manner. TeamCity provides this for us. ### 35. Great product for any sized development team **Rating:** 4.0/5.0 stars **Reviewed by:** Marian L. | Application Developer, Non-Profit Organization Management, Mid-Market (51-1000 emp.) **Reviewed Date:** May 01, 2015 **What do you like best about TeamCity?** I like the application's main function: to automate different aspects of the software development life cycle. I also like that it has different runners for different types of applications (webdeploy, node, etc.) **What do you dislike about TeamCity?** I dislike the fact that it does not explain software specific terminology (build, check-in, pipeline, etc.) very well. Most of the time I would have to search the internet to figure out what these terms mean. **Recommendations to others considering TeamCity:** 1. Make sure you have a lot of tech resources (both "materials" and labor) on hand; depending on the size of your company you may need to have an infrastructure just for your continuous integration needs 2. Be prepared to know what a "build" is beforehand and the other terminology associated with TeamCity **What problems is TeamCity solving and how is that benefiting you?** The main business problem we are trying to solve is automating parts of the software development life cycle. By automating many things, we are able to gain productivity, decrease time in deploying software from one environment to another, keep track of deployment process configurations easily, and so much more. ### 36. Great Continuous Integration Tool **Rating:** 4.0/5.0 stars **Reviewed by:** Paolo D. | Software Developer in Test, Mid-Market (51-1000 emp.) **Reviewed Date:** May 06, 2015 **What do you like best about TeamCity?** Long but simple process to setup any build, with the possibility to customize many options, schedule a build trigger, create builds from the same chain. In order to get started, you need just few clicks, while a more advanced usage is always two clicks away **What do you dislike about TeamCity?** Tooltips could give more meaningful and immediate feedback, rather than opening in a generic window with a lot of information **What problems is TeamCity solving and how is that benefiting you?** I reduced the working time needed to run the acceptance tests by running them overnight, catch the false failures and rerun them overnight, so build status can be determined in the morning In addition, live smoke tests are continuously, giving us an immediate feedback on the live servers, and acceptance tests for the API are run as soon as a commit is done, both the the test suite and the code base ### 37. Great build manager **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Utilities | Mid-Market (51-1000 emp.) **Reviewed Date:** May 19, 2015 **What do you like best about TeamCity?** It suits our work environment as we are continuously integrating and expanding. It is quite straight forward to use. **What do you dislike about TeamCity?** It can be difficult to interpret test failures using the service and the layout can look crowded. **What problems is TeamCity solving and how is that benefiting you?** We have a number of environments and services so this suits us well as it can be extended and expanded to fit all of these projects in. ### 38. My QA experience with TC spans 5 months in a professional setting and so far seems straigh forward **Rating:** 4.0/5.0 stars **Reviewed by:** Jordan P. | Selenium Developer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** May 07, 2015 **What do you like best about TeamCity?** Simplicity in building projects that development has passed down to be tested as well as running our Selenium Tests on it. **What do you dislike about TeamCity?** Although I didn't set up the project I can see it being a bit of a monster to understand set up. **What problems is TeamCity solving and how is that benefiting you?** Testing Web Applications by frequently updating builds on servers run by TC. ### 39. TeamCity is one of the best tools as part of continuous delivery. **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** May 12, 2015 **What do you like best about TeamCity?** Build configuration provides significant flexibility, allowing for the compilation of source code with various targets, shell scripting, and more. **What do you dislike about TeamCity?** More flexibility is needed. For example, I only want to deploy my application if the build is for the source in the main repository, but not when it's for source branches. It's kind of tricky to output customized TeamCity logs. **Recommendations to others considering TeamCity:** Create a more user-friendly API for the output of customized TeamCity logs. **What problems is TeamCity solving and how is that benefiting you?** Teamcity, as an automatic build tool, improves the efficiency of the entire continuous delivery process. ### 40. Not a fan **Rating:** 1.0/5.0 stars **Reviewed by:** Verified User in Computer Games | Small-Business (50 or fewer emp.) **Reviewed Date:** May 28, 2015 **What do you like best about TeamCity?** The interface is nice and has a large amount of options **What do you dislike about TeamCity?** Documentation sucks, and is very difficult to set up and upgrade **What problems is TeamCity solving and how is that benefiting you?** we use this for automated builds. **Official Response from Yegor Naumov:** > Hi, Thanks for your review. Could you please elaborate on what exactly were your pain points with setup and upgrade? Did you use the set up from URL feature which lets you create a project by simply providing a URL to your VCS? What exactly caused the difficulties while upgrading? Did you not like the format or the contents of the documentation? Do you think it is not full enough? If so, in which section? Thanks for your answers beforehand. ## TeamCity Discussions - [What is TeamCity used for?](https://www.g2.com/discussions/what-is-teamcity-used-for) - 1 comment, 1 upvote - [What is the difference between Jenkins and TeamCity?](https://www.g2.com/discussions/what-is-the-difference-between-jenkins-and-teamcity) - 1 comment, 1 upvote - [Is TeamCity a continuous integration tool?](https://www.g2.com/discussions/is-teamcity-a-continuous-integration-tool) - 1 comment, 1 upvote - [What is TeamCity in Devops?](https://www.g2.com/discussions/what-is-teamcity-in-devops) - 1 comment, 1 upvote - [What is the use of TeamCity?](https://www.g2.com/discussions/what-is-the-use-of-teamcity) - 1 comment, 1 upvote - [View TeamCity pricing details and edition comparison](https://www.g2.com/products/teamcity/reviews?page=2§ion=pricing&secure%5Bexpires_at%5D=2026-07-23+14%3A06%3A56+-0500&secure%5Bsession_id%5D=561176c1-2e9f-42b7-86c6-58b5a0a19d11&secure%5Btoken%5D=6e6c47b1553274d8bc39b03f7e6fb015fe7cd6389dae6c3cec940d47ebd04e39&format=llm_user) ## TeamCity Integrations - [Bitbucket](https://www.g2.com/products/bitbucket/reviews) - [GitLab](https://www.g2.com/products/gitlab/reviews) - [Jira](https://www.g2.com/products/jira/reviews) ## TeamCity Features **Functionality** - Deployment-Ready Staging - Integration - Extensible **Functionality** - Integrations - Extensibility - Test Customization **Management** - Processes and Workflow - Reporting - Automation **Management** - Automation - Processes and Workflow - Reporting **Agentic AI - Continuous Integration** - Autonomous Task Execution - Cross-system Integration - Adaptive Learning - Natural Language Interaction - Proactive Assistance **Agentic AI - Continuous Delivery** - Autonomous Task Execution - Cross-system Integration - Adaptive Learning - Natural Language Interaction - Proactive Assistance ## Top TeamCity Alternatives - [Red Hat Ansible Automation Platform](https://www.g2.com/products/red-hat-ansible-automation-platform/reviews) - 4.6/5.0 (369 reviews) - [Bamboo](https://www.g2.com/products/bamboo/reviews) - 4.1/5.0 (68 reviews) - [Jenkins](https://www.g2.com/products/jenkins/reviews) - 4.4/5.0 (557 reviews)