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

Jenkins vs TeamCity comparison

 

Comparison Buyer's Guide

Executive Summary
 

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
9th
Average Rating
8.2
Number of Reviews
28
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of December 2024, in the Build Automation category, the mindshare of Jenkins is 11.5%, down from 14.4% compared to the previous year. The mindshare of TeamCity is 7.0%, up from 6.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

AllenUmlas - PeerSpot reviewer
Streamlines the CI/CD process with its user-friendly interface, extensive plugin ecosystem and efficient automation capabilities
Jenkins is incredibly user-friendly, so I haven't encountered any difficulties using it. It's the only product I've used for automation, but I find it to be very intuitive and effective. Jenkins has been instrumental in automating our build and deployment processes. We're leveraging Jenkins to automate tasks related to Telco, particularly in upgrading the manual orchestration. It's a critical tool for streamlining our operations.
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

"Also, the ability to customize these plugins is valuable. Its user-friendliness stands out, especially in its user interface which allows easy installation and configuration."
"The most valuable features of Jenkins are the ease of use and the information about how to use the features is readily available on the internet. Additionally, with the solution, I can use other reporting tools, such as Flow."
"Jenkins is particularly valuable since it saves time by automating manual tasks."
"Having builds and test tasks triggered on commit helps not to break the product."
"Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead."
"Jenkins has excellent task planning features."
"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 initial setup is pretty simple."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"Using TeamCity and emailing everyone on fail is one way to emphasize the importance of testing code and showing management why taking the time to test actually does saves time from having to fix bugs on the other end."
"TeamCity's GUI is nice."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"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."
"TeamCity is a very user-friendly tool."
 

Cons

"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."
"The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift."
"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."
"Centralized user management would be helpful."
"Jenkins could improve the integration with other platforms."
"Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"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."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"REST API support lacks many features in customization of builds, jobs, and settings."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"If there was more documentation that was easier to locate, it would be helpful for users."
"We've called TeamCity tech support. Unfortunately, all their tech support is based in Europe, so we end up with such a big time crunch that I now need to have one person in the US."
"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."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
 

Pricing and Cost Advice

"Jenkins is not expensive and reasonably priced."
"Jenkins is open-source, so it is free."
"The tool is open-source."
"​It is free.​"
"It is a free product."
"In our company, we do pay for the licensing of the solution."
"Jenkins is an open-source platform."
"It is a cheap solution."
"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.
824,053 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
23%
Computer Software Company
16%
Manufacturing Company
11%
Government
6%
Financial Services Firm
27%
Computer Software Company
18%
Manufacturing Company
7%
Real Estate/Law Firm
4%
 

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

 

Learn More

 

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: December 2024.
824,053 professionals have used our research since 2012.