GoCD vs Jenkins comparison

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

"The UI is colorful."

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

"I like the business logs. It's a very useful tool. Client-server communication is also very fast."

"It is open source, flexible, scalable, and easy to use. It is easy to maintain for the administrator. It is a continuous integration tool, and its enterprise version is quite mature. It has good integrations and plug-ins. Azure DevOps can also be integrated with Jenkins."

"I like that you can find a wide range of plugins for Jenkins."

"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. You can just build one container in it and deploy it."

"Jenkins's automation and orchestration features have significantly improved workflows by automating various processes. Initially, it did not support YAML manifesting or GitOps, but recent versions have introduced these capabilities. Now, the tool supports importing manifest files from Git repositories, enabling the implementation of GitOps pipelines. Compared to other tools like GitLab, it has become a mature tool for running CI/CD pipelines."

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

"Jenkins is very user-friendly."

"Jenkins has been instrumental in automating our build and deployment processes."

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

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

"The tool must be more user-friendly."

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

"Centralized user management would be helpful."

"The documentation on plugin development could be better: more examples. ​"

"They need to improve their documentation."

"The solution could improve by having more advanced integrations."

"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."

"There is no way for the cloud repositories to trigger Jenkins."

"UI is quite outdated."

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

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

"The pricing for Jenkins is free."

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

"The tool is open-source."

"The solution is one of the lowest costs compared to competitors."

"Jenkins is open-source, so it is free."

"We are using the freeware version of Jenkins."

"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."

"It is a cheap solution."