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."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."
"Bamboo was used extensively in our organization for PCA compliance."
"In my experience Bamboo is scalable."
"Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process."
"It can do the CI pipeline well."
"One of the big things that made us choose Bamboo, is it seamlessly integrates its APIs into NetSuite, which is our main ELP system."
"The most valuable feature of Bamboo is that it is a good tool for CI/CD integration."
"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."
"Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available."
"The most valuable features of Jenkins are its ease of use and good plugins available. You are able to connect to a lot of solutions."
"Very easy to understand for newcomers."
"Configuration management: It is so easy to configure a Jenkins instance. Migrate configuration to a new environment just by copying XML files and setting up new nodes."
"Distributed execution of build and test jobs."
"Having builds and test tasks triggered on commit helps not to break the product."
"The initial setup is pretty simple."
"Jenkins' most valuable feature is Pipeline."
"The marketing strategy of Bamboo is an area of concern where improvements are needed."
"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 would be great if Bamboo could introduce a more containerized deployment model."
"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."
"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."
"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."
"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."
"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."
"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 scriptwriting process could be improved in this solution in the future."
"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."
"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."
"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"The support for the latest Java Runtime Environment should be improved."
"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."
Bamboo is ranked 5th in Build Automation with 20 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. Bamboo is rated 7.4, while Jenkins is rated 8.0. The top reviewer of Bamboo writes "High availability, helpful support, and plenty of plugins available". On the other hand, the top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". Bamboo is most compared with GitLab, GitHub Actions, Harness, Tekton and AWS CodePipeline, 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.
