GoCD vs Jenkins comparison

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

"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 is very stable."

"The most valuable feature is its ability to connect with different tools and technologies."

"It's very useful when you want to automate different processes from beginning to end."

"Jenkins is particularly valuable since it saves time by automating manual tasks."

"It has a lot of community posts and support."

"We benefit from Kubernetes' ability to autoscale pods and use horizontal pod autoscalers to adjust the number of pods based on metrics like CPU or memory usage, ensuring efficient resource allocation and stability under load."

"Also, the ability to customize these plugins is valuable. Its user-friendliness stands out, especially in its user interface which allows easy installation and configuration."

"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."

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

"It would be helpful if they had a bit more interactive UI."

"There are some issues with Jenkins, especially with the SIP job."

"Centralized user management would be helpful."

"This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful."

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

"The upgrades need improvement."

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

"The scriptwriting process could be improved in this solution in the future."

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

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

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

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

"The tool is open-source."

"There is no cost. It is open source."

"Jenkins is a free open-source server."

"​It is free.​"

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

"The pricing for Jenkins is free."