No more typing reviews! Try our Samantha, our new voice AI agent.

GoCD vs Jenkins comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

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

GoCD
Ranking in Build Automation
18th
Average Rating
7.6
Reviews Sentiment
7.1
Number of Reviews
7
Ranking in other categories
Application Lifecycle Management (ALM) Suites (17th), Release Automation (13th)
Jenkins
Ranking in Build Automation
1st
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
92
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Build Automation category, the mindshare of GoCD is 2.8%, up from 1.5% compared to the previous year. The mindshare of Jenkins is 9.1%, down from 10.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Jenkins9.1%
GoCD2.8%
Other88.1%
Build Automation
 

Featured Reviews

Nishant Narayan Singh - PeerSpot reviewer
DevOps Architect at a consultancy with 10,001+ employees
Simplifies the pipeline process, but the access control system needs enhancement
One area of product improvement is the access control system. It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be simplified. The folder structure is another aspect that could be enhanced, as all jobs are displayed on a single page without the clear organization seen in Jenkins. Implementing a more structured approach to organizing jobs would improve user experience. AI could simplify job creation. For example, instead of manually editing pipelines as code, an AI tool could allow users to input variables and automatically generate the required jobs. It would help reduce human errors, such as issues that arise from incorrect edits in large code files.
Mahdi Mallaki - PeerSpot reviewer
Senior Devops Engineer at a tech vendor with 10,001+ employees
Has a community of plugin providers but needs improvement in Kubernetes integration
Integrating Jenkins with other tools or solutions has presented some challenges. For instance, when attempting to integrate Jenkins with Kubernetes, I encountered numerous errors, which took several days to resolve. In Jenkins, adding a feature typically involves incorporating the repository feature separately. Jenkins lacks built-in Git repository functionality, necessitating an external Git repository to store Jenkins manifests. In contrast, GitLab offers an integrated Git repository and pipeline runner, streamlining the process. One improvement for Jenkins could be integrating a Git server, simplifying the management of CI/CD pipelines. Currently, with Jenkins, modifying pipeline manifests requires navigating to a separate Git repository. In GitLab, however, manifest changes can be made directly within the repository.

Quotes from Members

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

Pros

"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."
"GoCD's open-source nature is valuable."
"It has a user-friendly interface, which for free and open-source tools, the UI is really amazing and simple."
"Permission separations mean that we can grant limited permissions for each team or team member."
"In terms of value added it has more than achieved everything we wanted from it and more."
"After we switched to GO, each team can set-up their own delivery pipeline and run it themselves."
"The UI is colorful."
"The most valuable feature of the solution is its integration between different tools."
"Jenkins is a very good tool, which I highly recommend, and it's very helpful for the continuous integration of any products."
"Having builds and test tasks triggered on commit helps not to break the product."
"Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc."
"Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate."
"Jenkins has allowed for streamlined automated testing, building, and smoke testing of release candidates."
"The most beneficial thing is being able to do everything with just one click, which was not possible previously when any changes needed to be carried out manually."
"Jenkins is particularly valuable since it saves time by automating manual tasks."
 

Cons

"The documentation really should be improved by including real examples and more setup cases."
"The tool must be more user-friendly."
"It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be simplified."
"GO doesn't come with a lot of out of the box features like other tools, don't expect that you can get it to work by clicking the NEXT button."
"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."
"User management, Documentation, Advanced GUI functionality."
"It could be cheaper."
"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 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."
"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."
"Adding support for OIDC and internal user databases simultaneously would improve Jenkins."
"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."
"The usability and user interface could be improved."
"Pipelines are still young and promising. But this part still has some room for improvement."
 

Pricing and Cost Advice

"This is an open-source solution and it is inexpensive."
"It's an open-source and free tool."
"Jenkins is an open-source platform."
"The solution is one of the lowest costs compared to competitors."
"Jenkins is a free open-source server."
"Jenkins is open-source, so it is free."
"Jenkins is a free solution, it is open source."
"Jenkins is open source."
"Some of the add-ons are too expensive."
"It is a free product."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
896,803 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Computer Software Company
8%
Educational Organization
8%
University
8%
Financial Services Firm
19%
Manufacturing Company
13%
Computer Software Company
7%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise2
Large Enterprise3
By reviewers
Company SizeCount
Small Business27
Midsize Enterprise15
Large Enterprise58
 

Questions from the Community

What needs improvement with GoCD?
One area of product improvement is the access control system. It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be sim...
What is your primary use case for GoCD?
The solution helps us deploy microservices across multiple environments.
What advice do you have for others considering GoCD?
We integrate the solution with Git, where we store our code. We use Maven to build the code and tools like SonarQube and Checkmarx for code quality checks. We deploy our services in a Kubernetes-ba...
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 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 needs improvement with Jenkins?
I do not have any notes for improvement.
 

Comparisons

 

Also Known As

Adaptive ALM, Thoughtworks Go
No data available
 

Overview

 

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
Find out what your peers are saying about GoCD vs. Jenkins and other solutions. Updated: April 2026.
896,803 professionals have used our research since 2012.