Try our new research platform with insights from 80,000+ expert users

Jenkins vs TeamCity comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Jenkins
Ranking in Build Automation
3rd
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
93
Ranking in other categories
No ranking in other categories
TeamCity
Ranking in Build Automation
10th
Average Rating
8.2
Number of Reviews
28
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2025, in the Build Automation category, the mindshare of Jenkins is 11.0%, down from 14.2% compared to the previous year. The mindshare of TeamCity is 7.3%, up from 6.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Dinesh-Patil - PeerSpot reviewer
A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment
The dashboard needs to be improved. Though the access management and authentication functionalities are present, the dashboard and UI could be more user-friendly. The product has many plug-ins. Users have to go through the documentation to be able to use the product. The UI must be more user-friendly. The information should be available in the dashboard itself. The users shouldn’t have to refer to the documentation. When a user hovers over the elements on the dashboard, it should reveal information about them.
Omakoji Idakwoji - PeerSpot reviewer
Build management system used to successfully create full request tests and run security scans
I find the TeamCity backend easily accessible. Users can login to the Linux servers that TeamCity is installed on and perform operations. Also I find the ability to template solutions using the meta runner a good feature as well as the user management feature. There is a display that shows which user made recent changes to a branch on GitHub, including the time the changes were made and the particular agent that ran the job. This is also a very useful feature. The metrics and audit available for projects, pipelines and jobs come in handy when debugging.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The solution is scalable and concurrent users have access to the platform."
"Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases."
"We have started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable."
"The most valuable features of Jenkins are its ease of use and good plugins available. You are able to connect to a lot of solutions."
"The most valuable features of Jenkins are creating builds, and connecting them with Sonar for Sonar analysis. Additionally, we connect it with other vulnerability tools, such as WhiteSource which is useful."
"Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
"The most valuable feature of Jenkins is its open source."
"Jenkins is particularly valuable since it saves time by automating manual tasks."
"TeamCity is more structured and user-friendly than other vendors."
"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"The integration is a valuable feature."
"TeamCity is a very user-friendly tool."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
 

Cons

"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams."
"UI is quite outdated."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable."
"Adding support for OIDC and internal user databases simultaneously would improve Jenkins."
"The UI of Jenkins could improve."
"We cannot change the ownership of any directory or file or any kind of directory."
"The integration between other solutions and TeamCity could be smoother."
"REST API support lacks many features in customization of builds, jobs, and settings."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"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."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"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."
"I need some more graphical design."
 

Pricing and Cost Advice

"It could be cheaper because there are many solutions available in the market. We are paying yearly."
"It is a free product."
"Jenkins is not expensive and reasonably priced."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"Jenkins is open source."
"It's free software with a big community behind it, which is very good."
"Jenkins is an open-source tool."
"We are using the freeware version of Jenkins."
"Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most."
"The licensing is on an annual basis."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
832,138 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
Jan 22, 2015
I generally find TeamCity a lot more intuitive than Jenkins.
Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis…
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Computer Software Company
17%
Manufacturing Company
11%
Government
6%
Financial Services Firm
27%
Computer Software Company
17%
Manufacturing Company
7%
Government
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

How does Tekton compare with Jenkins?
When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very e...
What do you like most about Jenkins?
Jenkins has been instrumental in automating our build and deployment processes.
What is your experience regarding pricing and costs for Jenkins?
Jenkins is used in many companies to save money, especially within R&D divisions, by avoiding the expenses of proprietary tools.
What do you like most about TeamCity?
One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies.
What is your experience regarding pricing and costs for TeamCity?
Compared to new technologies, TeamCity is more expensive and is an older tool compared to tools like GitLab.
What needs improvement with TeamCity?
TeamCity's user interface could be improved; specifically, the tree structure on the homepage is not clear, making it difficult to search for projects. Moreover, there are some limitations related ...
 

Comparisons

 

Overview

 

Sample Customers

Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about Jenkins vs. TeamCity and other solutions. Updated: January 2025.
832,138 professionals have used our research since 2012.