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."Permission separations mean that we can grant limited permissions for each team or team member."
"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."
"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."
"This solution has helped us in automating the build and test process, reducing time."
"GitHub linking is pretty good. We have a deployment application where we can run our tests and add various variables to be passed as assertions to those tests. This is pretty fluid with Jenkins."
"I like that you can find a wide range of plugins for Jenkins."
"Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline."
"The solution is scalable and concurrent users have access to the platform."
"It is very useful for us to be able to collect and manage automatic processing pipelines."
"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 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."
"The documentation on plugin development could be better: more examples. "
"Logging could be improved to offer a clearer view."
"The bug fix speed is very slow."
"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."
"The solution's UI can use a facelift and the logs can use more detailed information."
"There is no way for the cloud repositories to trigger Jenkins."
"It would be helpful if they had a bit more interactive UI."
"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."
GoCD is ranked 10th in Build Automation with 6 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. GoCD is rated 7.6, 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, Microsoft Azure DevOps, Tekton, GitHub Actions and AWS CodePipeline, 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.