Jenkins vs TeamCity comparison

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

Jenkins

Read 90 Jenkins reviews

5,264 Views
4,524 Comparison Views

87% willing to recommend

TeamCity

Read 28 TeamCity reviews

2,643 Views
2,335 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: October 2024).

Buyer's Guide

Jenkins vs. TeamCity

October 2024

Download the complete report

Helped 816,406 peers since 2012

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

10th

Average Rating

8.2

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of November 2024, in the Build Automation category, the mindshare of Jenkins is 11.3%, down from 14.5% compared to the previous year. The mindshare of TeamCity is 6.8%, down from 7.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Build Automation

Featured Reviews

AllenUmlas

Engineer at Etisalat

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.

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

"I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company."

"Jenkins is very easy to use."

"It's very easy to learn."

"Jenkins has excellent task planning features."

"A lot of support material exists via a single web search of exactly what you're looking for."

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

"Jenkins's open-based framework is very valuable."

"The most valuable features of Jenkins are the integration with GitHub, and the automation for deployment."

More Jenkins pros

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

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

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

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

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

"I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC."

"VCS Trigger: Provides excellent source control support."

More TeamCity pros

Cons

"The solution could improve by having more advanced integrations."

"Jenkins could simplify the user interface a little bit because it sometimes creates too many features cramped in the UI."

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

"Jenkins could improve by adding the ability to edit test automation and make time planning better because it is difficult. It should be easier to do."

"Jenkins needs a faster deployment process."

"The enterprise version is less stable than the open-source version."

"The disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy."

"Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."

More Jenkins cons

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

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

"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 there was more documentation that was easier to locate, it would be helpful for users."

"I need some more graphical design."

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

"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."

"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."

More TeamCity cons

Pricing and Cost Advice

"Jenkins is an open-source tool."

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

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

"Jenkins is open-source, so it is free."

"Jenkins is open source and free."

"I used the free OSS version all the time. It was enough for all my needs."

"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."

"We are using the freeware version of Jenkins."

More Jenkins pricing and cost advice

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

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

816,406 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

23%

Computer Software Company

16%

Manufacturing Company

11%

Government

Financial Services Firm

28%

Computer Software Company

17%

Manufacturing Company

Government

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?

I do not have extensive knowledge on the pricing or licensing aspect as I used Jenkins for free at the local machine level. However, it is generally regarded as cost-effective.

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 17% of the time

Bamboo vs Jenkins

Compared 14% of the time

Harness vs Jenkins

Compared 10% of the time

AWS CodePipeline vs Jenkins

Compared 9% of the time

JFrog Pipeline vs Jenkins

Compared 4% of the time

More Jenkins Competitors

GitLab vs TeamCity

Compared 38% of the time

GitHub Actions vs TeamCity

Compared 16% of the time

CircleCI vs TeamCity

Compared 12% of the time

Harness vs TeamCity

Compared 10% of the time

Bamboo vs TeamCity

Compared 2% of the time

More TeamCity Competitors

Product Reports

Buyer's Guide

Jenkins

November 2024

Download Jenkins product report

Buyer's Guide

TeamCity

October 2024

Download TeamCity product report

Learn More

Jenkins

JetBrains

Overview

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

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.

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

October 2024

Free Report: Jenkins vs. TeamCity

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

DOWNLOAD NOW

816,406 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.