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.
JI
Principal Software Engineer at a financial services firm with 5,001-10,000 employees
Efficient resource allocation and robust workflow with autoscaling capabilities
In Kubernetes, we use node-based architecture with nodes and pods and follow practices like RBAC and rollback. Multiple pods can run concurrently. We benefit from Kubernetes' ability to autoscale pods and use horizontal pod autoscalers to adjust the number of pods based on metrics like CPU or memory usage, ensuring efficient resource allocation and stability under load.

Quotes from Members

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

Pros

"It has a user-friendly interface, which for free and open-source tools, the UI is really amazing and simple."
"The UI is colorful."
"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."
"In terms of value added it has more than achieved everything we wanted from it and more."
"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."
"Jenkins has excellent task planning features."
"We benefit from Kubernetes' ability to autoscale pods and use horizontal pod autoscalers to adjust the number of pods based on metrics like CPU or memory usage, ensuring efficient resource allocation and stability under load."
"We use it for the automation pipeline in our development of software, where it compiles and moves the software to deployment in the Microsoft Azure cloud and also generates documentation for all the software."
"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, and you can just build one container in it and deploy it."
"Jenkins is a very good tool, which I highly recommend, and it's very helpful for the continuous integration of any products."
"I like that you can find a wide range of plugins for Jenkins."
"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."
"Using Jenkins we have configured and automated the complete build procedure."
 

Cons

"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."
"The tool must be more user-friendly."
"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."
"It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be simplified."
"The documentation really should be improved by including real examples and more setup cases."
"It would help if they offered more integrations."
"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"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."
"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."
"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."
"And I don't care too much for the Jenkins user interface. It's not that user-friendly compared to other solutions available right now. It's not a great user experience. You can do just fine if you are a techie, but it would take a novice some time to learn it and get things done."
"The user interface could be updated a little."
"The solution could improve by having more advanced integrations."
 

Pricing and Cost Advice

"It's an open-source and free tool."
"This is an open-source solution and it is inexpensive."
"It is an open source."
"The tool is open-source."
"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."
"Some of the add-ons are too expensive."
"It's free software with a big community behind it, which is very good."
"We are using the freeware version of Jenkins."
"There is no cost. It is open source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
900,051 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Manufacturing Company
10%
Construction Company
8%
Computer Software Company
7%
Financial Services Firm
19%
Manufacturing Company
14%
Construction Company
7%
Comms Service Provider
6%
 

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: June 2026.
900,051 professionals have used our research since 2012.