Try our new research platform with insights from 80,000+ expert users

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
17th
Average Rating
7.6
Reviews Sentiment
7.1
Number of Reviews
7
Ranking in other categories
Application Lifecycle Management (ALM) Suites (18th), Release Automation (13th)
Jenkins
Ranking in Build Automation
4th
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 March 2026, in the Build Automation category, the mindshare of GoCD is 2.4%, up from 1.5% compared to the previous year. The mindshare of Jenkins is 7.3%, down from 10.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Jenkins7.3%
GoCD2.4%
Other90.3%
Build Automation
 

Featured Reviews

RajeshReddy - PeerSpot reviewer
Dev Ops Engineer at Infosys
The UI is colorful, but the user experience must be improved
We can see all the pipelines with a simple search. The UI is colorful. The user experience is very rich. The product is very easy to learn if we know a bit of the basics. If we have someone to show us how to use it, it is very easy.
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 UI is colorful."
"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."
"In terms of value added it has more than achieved everything we wanted from it and more."
"GoCD's open-source nature is valuable."
"Permission separations mean that we can grant limited permissions for each team or team member."
"After we switched to GO, each team can set-up their own delivery pipeline and run it themselves."
"I like the business logs. It's a very useful tool. Client-server communication is also very fast."
"I like that you can find a wide range of plugins for Jenkins."
"Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
"Jenkins's automation and orchestration features have significantly improved workflows by automating various processes. Initially, it did not support YAML manifesting or GitOps, but recent versions have introduced these capabilities. Now, the tool supports importing manifest files from Git repositories, enabling the implementation of GitOps pipelines. Compared to other tools like GitLab, it has become a mature tool for running CI/CD pipelines."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"Jenkins is a CI/CD tool and is the most robust tool."
"Configuration management: It is so easy to configure a Jenkins instance. Migrate configuration to a new environment just by copying XML files and setting up new nodes."
"Jenkins has built good plugins and has a good security platform."
 

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."
"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."
"User management, Documentation, Advanced GUI functionality."
"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."
"A more user-friendly UI for creating pipelines would be helpful."
"The solution could improve by having more advanced integrations."
"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."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"Creating a new SonarQube project requires a separate job, and we've encountered some integration issues with Docker and the need for better vulnerability checks."
"The major drawback with Jenkins is the lack of support."
"I do not have any notes for improvement."
"The enterprise version is less stable than the open-source version."
 

Pricing and Cost Advice

"This is an open-source solution and it is inexpensive."
"It's an open-source and free tool."
"The pricing for Jenkins is free."
"The solution is one of the lowest costs compared to competitors."
"Jenkins is open source."
"Jenkins is an open-source platform."
"There is no cost. It is open source."
"We are using the freeware version of Jenkins."
"Jenkins is a free solution, it is open source."
"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
884,873 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
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…
 

Top Industries

By visitors reading reviews
Computer Software Company
10%
Retailer
8%
Educational Organization
8%
Financial Services Firm
8%
Financial Services Firm
17%
Manufacturing Company
15%
Computer Software Company
9%
Government
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 Business28
Midsize Enterprise15
Large Enterprise57
 

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.
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: March 2026.
884,873 professionals have used our research since 2012.