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."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."
"Permission separations mean that we can grant limited permissions for each team or team member."
"The most valuable features of Jenkins are creating builds, and connecting them with Sonar for Sonar analysis. Additionally, we connect it with other vulnerability tools, such as WhiteSource which is useful."
"The most valuable features of Jenkins are the ease of use and the information about how to use the features is readily available on the internet. Additionally, with the solution, I can use other reporting tools, such as Flow."
"Jenkins has been instrumental in automating our build and deployment processes."
"Jenkins has built good plugins and has a good security platform."
"I like that you can find a wide range of plugins for Jenkins."
"Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases."
"The most valuable feature of the solution is its integration between different tools."
"Jenkins is very 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."
"The tool must be more user-friendly."
"The documentation really should be improved by including real examples and more setup cases."
"It can be improved by including automated mobile reporting integrations."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"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."
"Partition security for the workflow of projects is not yet an option."
"Logging could be improved to offer a clearer view."
"Support should be provided at no cost, as there is no free support available for any of the free versions."
"The support for the latest Java Runtime Environment should be improved."
"The learning curve is quite steep at the moment."
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.