We performed a comparison between Bamboo 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."The most valuable feature of Bamboo is that it is a good tool for CI/CD integration."
"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."
"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."
"In my experience Bamboo is scalable."
"The most useful feature of Bamboo is its integration with other solutions such as Jira and BitBucket, also offered by Atlassian. It is easier to use tools all provided by one vendor."
"In Bamboo, build and deployment have been segregated. The build plan and deployment plan are different. When comparing Bamboo to other solutions, the native feature you will not find in another tool, such as Jenkins. They have segregated the build and deployment plan. This means, building the application and deploying it are two separate parts in Bamboo, they have segregated it apart from the UI. This makes the tool a bit better compared to other tools."
"Bamboo was used extensively in our organization for PCA compliance."
"Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline."
"This is a great integration tool and very powerful."
"We have started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable."
"We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent."
"We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity."
"Jenkins's open-based framework is very valuable."
"The most valuable feature of the solution is its integration between different tools."
"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"Bamboo is a bit complicated to use compared to other solutions, such as GitLab. You have to integrate different actions that are difficult that could be made easier."
"It's a little outdated. It's three years old."
"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."
"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."
"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."
"The marketing strategy of Bamboo is an area of concern where improvements are needed."
"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’s technical support services, in terms of speed of response, need improvement."
"Sometimes you have Jenkins restarting because of OOM errors."
"There is no way for the cloud repositories to trigger Jenkins."
"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."
"And I don't care too much for the Jenkins user interface. It's not that user-friendly compared to other solutions available right now. It's not a great user experience. You can do just fine if you are a techie, but it would take a novice some time to learn it and get things done."
"The user interface could be updated a little."
"I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it."
"The support for the latest Java Runtime Environment should be improved."
"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."
Bamboo is ranked 5th in Build Automation with 6 reviews while Jenkins is ranked 2nd in Build Automation with 39 reviews. Bamboo is rated 7.4, while Jenkins is rated 8.0. The top reviewer of Bamboo writes "Useful connector marketplace, customizable, and highly scalable". On the other hand, the top reviewer of Jenkins writes "Open-source and reliable but needs better documentation". Bamboo is most compared with GitLab, Tekton, Harness, GitHub Actions and Microsoft Azure, whereas Jenkins is most compared with GitLab, AWS CodePipeline, IBM Rational Build Forge, Tekton and Harness. See our Bamboo 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.