GoCD vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
Thoughtworks Logo
1,231 views|977 comparisons
Jenkins Logo
7,158 views|6,126 comparisons
Comparison Buyer's Guide
Executive Summary

We performed a comparison between GoCD and Jenkins 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 GoCD vs. Jenkins 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
"Permission separations mean that we can grant limited permissions for each team or team member.""The most notable aspect is its user interface, which we find to be user-friendly and straightforward for deploying and comprehending pipelines. We have the ability to create multiple pipelines, and in addition to that, the resource consumption is impressive."

More GoCD Pros →

"We used it for all continuous integration parts, like automation testing, deployment, etc.""Very easy to understand for newcomers.""The most valuable feature of the solution is its integration between different tools.""The most valuable feature of Jenkins is its open source.""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 simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly.""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.""Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline."

More Jenkins Pros →

Cons
"The aspect that requires attention is the user management component. When integrating with BitLabs and authenticating through GitLab, there are specific features we desire. One important feature is the ability to import users directly from GitLab, along with their respective designations, and assign appropriate privileges based on that information. Allocating different privileges to users is a time-consuming process for us.""The documentation really should be improved by including real examples and more setup cases."

More GoCD Cons →

"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.""Sometimes you have Jenkins restarting because of OOM errors.""Jenkins is not an easy solution to use and the configuration is not simple. They can improve the solution by adding a graphical interface that is more user-friendly.""Partition security for the workflow of projects is not yet an option.""It could be cheaper.""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.""I sometimes face a bottleneck when installing the plugins on an offline machine. Mapping the dependencies and then installing the correct sequence of dependencies is a nightmare, and it took me two days to do it.""Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."

More Jenkins Cons →

Pricing and Cost Advice
  • "It's an open-source and free tool."
  • "This is an open-source solution and it is inexpensive."
  • More GoCD 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 →

    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:The most notable aspect is its user interface, which we find to be user-friendly and straightforward for deploying and comprehending pipelines. We have the ability to create multiple pipelines, and in… more »
    Top Answer:GoCD could cover the authentication aspect. Currently, we are handling an in-house development that needs this. Comprehensive features must be established before transitioning into an enterprise… more »
    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.
    Ranking
    8th
    out of 41 in Build Automation
    Views
    1,231
    Comparisons
    977
    Reviews
    3
    Average Words per Review
    631
    Rating
    8.3
    2nd
    out of 41 in Build Automation
    Views
    7,158
    Comparisons
    6,126
    Reviews
    37
    Average Words per Review
    388
    Rating
    7.8
    Comparisons
    GitLab logo
    Compared 28% of the time.
    Tekton logo
    Compared 12% of the time.
    Microsoft Azure DevOps logo
    Compared 12% of the time.
    GitHub Actions logo
    Compared 10% of the time.
    CircleCI logo
    Compared 8% of the time.
    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.
    Tekton logo
    Compared 7% of the time.
    Also Known As
    Adaptive ALM, Thoughtworks Go
    Learn More
    Overview
    GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers businesses a first-class build and deployment engine for complete control and visibility. It was designed for continuous delivery and the concepts essential to this practice are built in at the core.

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

    Sample Customers
    Ancestry.com, Barclay Card, AutoTrader, BT Financial Group, Gamesys, Nike, Vodafone, Haufe Lexware, Medidata, Hoovers
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    Top Industries
    VISITORS READING REVIEWS
    Computer Software Company20%
    Financial Services Firm15%
    Comms Service Provider12%
    Retailer10%
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm20%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    Company Size
    REVIEWERS
    Small Business43%
    Midsize Enterprise43%
    Large Enterprise14%
    VISITORS READING REVIEWS
    Small Business18%
    Midsize Enterprise13%
    Large Enterprise68%
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Buyer's Guide
    GoCD vs. Jenkins
    March 2024
    Find out what your peers are saying about GoCD vs. Jenkins and other solutions. Updated: March 2024.
    765,386 professionals have used our research since 2012.

    GoCD is ranked 8th in Build Automation with 5 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. GoCD is rated 8.0, while Jenkins is rated 8.0. The top reviewer of GoCD writes "User-friendly, useful multiple pipeline capabilities, and low resource consumption". On the other hand, the top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". GoCD is most compared with GitLab, Tekton, Microsoft Azure DevOps, GitHub Actions and CircleCI, whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Tekton. See our GoCD vs. Jenkins 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.