Jenkins vs TeamCity comparison

Cancel
You must select at least 2 products to compare!
Jenkins Logo
7,158 views|6,126 comparisons
JetBrains Logo
3,476 views|3,016 comparisons
Comparison Buyer's Guide
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 2024).
765,386 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud.""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.""It is easy to use.""Has enabled full automation of the company.""The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script.""Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc.""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.""For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance."

More Jenkins Pros →

"Good integration with IDE and JetBrains products.""TeamCity's GUI is nice.""The integration is a valuable feature.""We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted.""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.""It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack.""The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine.""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."

More TeamCity Pros →

Cons
"Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on.""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.""Jenkins could simplify the user interface a little bit because it sometimes creates too many features cramped in the UI.""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.""It would be helpful if they had a bit more interactive UI.""This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager).""The scriptwriting process could be improved in this solution in the future.""Jenkins relies on the old version of interface for configuration management. This needs improvement."

More Jenkins Cons →

"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.""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.""It will benefit this solution if they keep up to date with other CI/CD systems out there.""The upgrade process could be smoother. Upgrading major versions can often cause some pain.""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.""REST API support lacks many features in customization of builds, jobs, and settings.""I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does.""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."

More TeamCity Cons →

Pricing and Cost Advice
  • "It is a free product."
  • "Jenkins is open source."
  • "​It is free.​"
  • "Some of the add-ons are too expensive."
  • "It's free software with a big community behind it, which is very good."
  • "I used the free OSS version all the time. It was enough for all my needs."
  • "Jenkins is open source and free."
  • "There is no cost. It is open source."
  • 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."
  • More TeamCity Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    765,386 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    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 nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Top Answer: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 easy… more »
    Top Answer:Jenkins has been instrumental in automating our build and deployment processes.
    Top Answer:TeamCity is a very user-friendly tool.
    Top Answer:It's open source, however, if you want your solution to be deployed on their cloud or on the cloud in general without you being involved and having it and managed by them, there may be costs involved… more »
    Top Answer:It's just a tool that I used. I needed to deliver something, so I did. I wasn't looking at it in a way to criticize it or to optimize it. As a user, I need some more graphical design. For example, in… more »
    Ranking
    2nd
    out of 41 in Build Automation
    Views
    7,158
    Comparisons
    6,126
    Reviews
    37
    Average Words per Review
    388
    Rating
    7.8
    6th
    out of 41 in Build Automation
    Views
    3,476
    Comparisons
    3,016
    Reviews
    2
    Average Words per Review
    574
    Rating
    8.0
    Comparisons
    GitLab logo
    Compared 16% of the time.
    Bamboo logo
    Compared 15% of the time.
    AWS CodePipeline logo
    Compared 9% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    Digital.ai Release  logo
    Compared 4% of the time.
    GitLab logo
    Compared 44% of the time.
    CircleCI logo
    Compared 17% of the time.
    Harness logo
    Compared 7% of the time.
    Tekton logo
    Compared 6% of the time.
    Bamboo logo
    Compared 5% of the time.
    Learn More
    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
    Top Industries
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm20%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    REVIEWERS
    Financial Services Firm14%
    Computer Software Company14%
    Consumer Goods Company7%
    Retailer7%
    VISITORS READING REVIEWS
    Financial Services Firm22%
    Computer Software Company14%
    Manufacturing Company10%
    Comms Service Provider7%
    Company Size
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    REVIEWERS
    Small Business38%
    Midsize Enterprise15%
    Large Enterprise46%
    VISITORS READING REVIEWS
    Small Business24%
    Midsize Enterprise10%
    Large Enterprise66%
    Buyer's Guide
    Jenkins vs. TeamCity
    March 2024
    Find out what your peers are saying about Jenkins vs. TeamCity and other solutions. Updated: March 2024.
    765,386 professionals have used our research since 2012.

    Jenkins is ranked 2nd in Build Automation with 83 reviews while TeamCity is ranked 6th in Build Automation with 24 reviews. Jenkins is rated 8.0, while TeamCity is rated 8.4. The top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Digital.ai Release , whereas TeamCity is most compared with GitLab, CircleCI, Harness, Tekton and Bamboo. 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.