Jenkins vs TeamCity comparison

Jenkins and JetBrains are both solutions in the Build Automation category. Jenkins is ranked #3 with an average rating of 8.1, while JetBrains is ranked #9 with an average rating of 6.8. Jenkins holds a 10.6% mindshare in BA, compared to JetBrains’s 7.6% mindshare. Additionally, 87% of Jenkins users are willing to recommend the solution, compared to 90% of JetBrains users who would recommend it.

Jenkins

Read 93 Jenkins reviews

4,377 Views
3,762 Comparison Views

87% willing to recommend

TeamCity

Read 28 TeamCity reviews

2,249 Views
2,013 Comparison Views

90% willing to recommend

Jenkins

TeamCity

Comparison Buyer's Guide

Download the report

Executive Summary

We performed a comparison between Jenkins and TeamCity based on real PeerSpot user reviews.

Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.

To learn more, read our detailed Jenkins vs. TeamCity Report (Updated: March 2025).

Buyer's Guide

Jenkins vs. TeamCity

March 2025

Download the complete report

Helped 839,422 peers since 2012

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

Ranking in other categories

No ranking in other categories

TeamCity

Ranking in Build Automation

9th

Average Rating

8.2

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of March 2025, in the Build Automation category, the mindshare of Jenkins is 10.6%, down from 14.0% compared to the previous year. The mindshare of TeamCity is 7.6%, up from 6.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Build Automation

Featured Reviews

Dinesh-Patil

Consultant at a manufacturing company with 10,001+ employees

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.

Read full review

Omakoji Idakwoji

Software Engineer at Home Depot

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.

Read full review

Quotes from Members

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

Pros

"Jenkins is very easy to use."

"It has a lot of community posts and support."

"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."

"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."

"With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."

"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."

"I love Jenkins. I like that you work on anything, and you make anything. Jenkins is very important for my team. I am satisfied with the product."

"The most valuable aspect of this solution is that there are multiple features. We can abstract certain variables and then build our deployment routine while being able to do some abstraction onto the SSH connections."

More Jenkins pros

"It's easy to move to a new release because of templates and meta-runners, and agent pooling."

"The integration is a valuable feature."

"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."

"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."

"Good integration with IDE and JetBrains products."

"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."

"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."

"The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications."

More TeamCity pros

Cons

"Partition security for the workflow of projects is not yet an option."

"The support for the latest Java Runtime Environment should be improved."

"I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it."

"Jenkins could improve the integration with other platforms."

"Logging could be improved to offer a clearer view."

"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."

"UI is quite outdated."

"Better and easy-to-use integration with Docker would be an improvement."

More Jenkins cons

"The integration between other solutions and TeamCity could be smoother."

"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 UI for this solution could be improved. New users don't find it easy to navigate. The need some level of training to understand the ins and the outs."

"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."

"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."

"It will benefit this solution if they keep up to date with other CI/CD systems out there."

More TeamCity cons

Pricing and Cost Advice

"Jenkins is a free open-source server."

"Jenkins is a free solution, it is open source."

"Jenkins is open source."

"It is a free product."

"The tool is open-source."

"This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved."

"The solution is open source."

"It is free."

More Jenkins pricing and cost advice

"The licensing is on an annual basis."

"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."

See which vendors are best for you

Use our free recommendation engine to learn which Build Automation solutions are best for your needs.

See recommendations

839,422 professionals have used our research since 2012.

Comparison Review

it_user184734

Systems Administrator at Facebook

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…

Read full review

Top Industries

By visitors reading reviews

Financial Services Firm

22%

Computer Software Company

18%

Manufacturing Company

11%

Government

Financial Services Firm

27%

Computer Software Company

17%

Manufacturing Company

Comms Service Provider

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...

See all answers

What do you like most about Jenkins?

Jenkins has been instrumental in automating our build and deployment processes.

See all answers

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.

See all answers

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.

See all answers

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.

See all answers

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 ...

See all answers

Comparisons

GitLab vs Jenkins

Compared 15% of the time

Harness vs Jenkins

Compared 14% of the time

Bamboo vs Jenkins

Compared 10% of the time

Bazel vs Jenkins

Compared 9% of the time

JFrog Pipeline vs Jenkins

Compared 5% of the time

More Jenkins Competitors

GitLab vs TeamCity

Compared 38% of the time

GitHub Actions vs TeamCity

Compared 18% of the time

Harness vs TeamCity

Compared 14% of the time

CircleCI vs TeamCity

Compared 10% of the time

Nx vs TeamCity

Compared 3% of the time

More TeamCity Competitors

Product Reports

Buyer's Guide

Jenkins

February 2025

Download Jenkins product report

Buyer's Guide

TeamCity

February 2025

Download TeamCity product report

Overview

Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

Jenkins

TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

JetBrains

Sample Customers

Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox

Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia

Buyer's Guide

Jenkins vs. TeamCity

March 2025

Free Report: Jenkins vs. TeamCity

Find out what your peers are saying about Jenkins vs. TeamCity and other solutions. Updated: March 2025.

DOWNLOAD NOW

839,422 professionals have used our research since 2012.

See our Jenkins vs. TeamCity report.

See our list of best Build Automation vendors.

We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.