Bamboo vs GoCD vs Jenkins comparison

"Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process."

"The most valuable features are compiling and deployment."

"We use Bamboo to automate all our test builds and deployments. It integrates with tools like the ReportPortal to help us check and evaluate processes. When we initiate commands, it automatically checks for scaling issues or failures related to new code. Based on these evaluations, it provides reports in the ReportPortal, helping us decide whether to implement changes."

"The most valuable features of Bamboo are its performance and UI. Additionally, there are a lot of useful plugins, integration with other solutions, such as Bitbucket and Jira, and a helpful online community."

"It's one of the best solutions in this line of work. We have many Atlassian products. We use Bamboo, JIRA, Service Desk, and some other Atlassian plugins. We like that it's easy to integrate into each other. It's a suite of services."

"One of the significant benefits of Bamboo is its built-in support for numerous clients and the ability to tailor its capabilities to your specific requirements. This high level of customization enables you to create pipelines that are ideally suited to your needs, making it an invaluable tool for conducting advanced testing."

"In my experience Bamboo is scalable."

"The tool is useful for continuous deployment."

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

"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 solution is scalable and has a large number of plugins that can help you scale it to your needs."

"Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline."

"It's very easy to learn."

"We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc."

"GitHub linking is pretty good. We have a deployment application where we can run our tests and add various variables to be passed as assertions to those tests. This is pretty fluid with Jenkins."

"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."

"I can install Jenkins for integration from multiple developers and automate application delivery, staging, and production environments."

"Bamboo could improve by having compatibility with GitLab. It would be better to have this platform for deploying code and storing container registries. Bamboo does not have a container registry. Additionally, there could be more features added."

"Bamboo can improve by providing more with scripting, such as they have with Jenkins. Bamboo is more UI-driven at this time, Jenkins is going in that direction too."

"Bamboo’s technical support services, in terms of speed of response, need improvement."

"It's a little outdated. It's three years old."

"One area that could be enhanced is the governance process, particularly with regard to building approvals and transitions between stages. In comparison to other solutions, such as Jira, which features a workflow that supports approval processes, this capability is not natively available in Bamboo. To implement this functionality, integration with other solutions, such as GSM may be necessary. Although some add-ons, such as Adaptavist ScriptRunner, are available in the market to circumvent this limitation, they may not offer the exact functionality needed. Therefore, there is certainly room for improvement in this area."

"The solution needs to support more customization in the training. What's offered is pretty generic. They need better training and should offer more guidance."

"Scalability depends on the use case. If it is really a big customer with a lot of tests, it might not be a scalable option for them."

"It should be much easier to use. It shouldn't require a lot of reading to be able to use it. It should have just two or three screens rather than hundreds of screens requiring a lot of clicking. It also requires a lot of integration. It has a steep learning curve. It takes a lot of time to understand and put in the data. There is also no proper training."

"The tool must be more user-friendly."

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

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

"Performance-wise. This needs to be improved. Not only performance-wise, some functionality or some features can be added to Jenkins."

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

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

"Improvement-wise, I would want the solution's user interface to be changed for the better. In short, the solution can be made more user-friendly."

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

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

"It does not have a very user-friendly interface."

"Jenkins needs a faster deployment process."

"If Bamboo could provide more flexibility on pricing, that would help. On the agent side, if you want to increase the number of agents it should be less expensive. If they can provide some better pricing model, it will help, whether we are going to use it or are already using it."

"There is a subscription required to use Bamboo."

"The price of Bamboo is reasonable."

"I rate the solution's pricing a three out of five."

"The server products for small teams used to offer excellent pricing. However, Atlassian has since changed the offering and the pricing is more expensive. I do still think the solution offers good value for money."

"I rate the product’s pricing a five out of ten."

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

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

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

"​It is free.​"

"It is an open source."

"Jenkins is open source."

"I used the free OSS version all the time. It was enough for all my needs."

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

"It is a free product."

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