GoCD vs Jenkins comparison

"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."

"GoCD's open-source nature is valuable."

"Jenkins' most valuable feature is Pipeline."

"Distributed execution of build and test jobs."

"The most valuable feature of the solution is its integration between different tools."

"The initial setup is pretty simple."

"There are a large number of plugins available for integration with third party systems."

"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."

"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."

"It is easy to use."

"The documentation really should be improved by including real examples and more setup cases."

"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."

"It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be simplified."

"The user interface could be updated a little."

"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."

"A more user-friendly UI for creating pipelines would be helpful."

"We sometimes face challenges during version upgrades, such as failures when migrating Kubernetes versions."

"It would be better if there were an option to remove its Java dependency. This would make it more compatible with other software, and it could be much better. At present, we have to depend on Java whenever we want to deploy agents."

"I would like to see even more integrations included in the next release."

"We cannot change the ownership of any directory or file or any kind of directory."

"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."

"This is an open-source solution and it is inexpensive."

"It's an open-source and free tool."

"The open-source version is free, but small companies would not be able to afford the cloud-based version."

"We are using the free version of Jenkins. There are no costs or licensing."

"Some of the add-ons are too expensive."

"Jenkins is not expensive and reasonably priced."

"​It is free.​"

"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."

"Jenkins is a free solution, it is open source."

"It is a cheap solution."