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 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."
"The UI is colorful."
"Jenkins has a lot of built-in packages and tools."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."
"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 Jenkins is its open source."
"Distributed execution of build and test jobs."
"It's very useful when you want to automate different processes from beginning to end."
"The automated elements are easy to use and you can put them into your server."
"The documentation really should be improved by including real examples and more setup cases."
"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."
"I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information."
"We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms."
"A more user-friendly UI for creating pipelines would be helpful."
"The UI must be more user-friendly."
"Jenkins could improve the integration with other platforms."
"Some kind of SaaS product would be helpful in providing organizational structure."
"We cannot change the ownership of any directory or file or any kind of directory."
"The UI of Jenkins could improve."
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.