We performed a comparison between Bamboo and Chef 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."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 platform helps us with automated and timely backup. It provides data replication as well."
"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."
"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 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."
"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."
"The most valuable feature of Bamboo is that it is a good tool for CI/CD integration."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"Chef recipes are easy to write and move across different servers and environments."
"The scalability of the product is quite nice."
"Manual deployments came to a halt completely. Server provisioning became lightning fast. Chef-docker enabled us to have fewer sets of source code for different purposes. Configuration management was a breeze and all the servers were as good as immutable servers."
"The most valuable feature is the language that it uses: Ruby."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"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 performance around the deployment feature could be improved."
"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."
"The marketing strategy of Bamboo is an area of concern where improvements are needed."
"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."
"It would be great if Bamboo could introduce a more containerized deployment model."
"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."
"I would also like to see more analytics and reporting features. Currently, the analytics and reporting features are limited. I'll have to start building my own custom solution with Power BI or Tableau or something like that. If it came with built-in analytics and reporting features that would be great."
"The time that it takes in terms of integration. Cloud integration is comparatively easy, but when it comes to two-link based integrations - like trying to integrate it with any monitoring tools, or maybe some other ticketing tools - it takes longer. That is because most of the out-of-the-box integration of the APIs needs some revisiting."
"I would rate this solution a nine because our use case and whatever we need is there. Ten out of ten is perfect. We have to go to IOD and stuff so they should consider things like this to make it a ten."
"I would like them to add database specific items, configuration items, and migration tools. Not necessarily on the builder side or the actual setup of the system, but more of a migration package for your different database sets, such as MongoDB, your extenders, etc. I want to see how that would function with a transition out to AWS for Aurora services and any of the RDBMS packages."
"They could provide more features, so the recipes could be developed in a simpler and faster way. There is still a lot of room for improvement, providing better functionalities when creating recipes."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"There appears to be no effort to fix the command line utility functionality, which is definitely broken, provides a false positive for a result when you perform the operation, and doesn't work."
Bamboo is ranked 5th in Build Automation with 20 reviews while Chef is ranked 15th in Build Automation with 18 reviews. Bamboo is rated 7.4, while Chef 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 Chef writes "Easy configuration management, optimization abilities, and complete infrastructure and application automation". Bamboo is most compared with GitLab, Jenkins, GitHub Actions, Harness and Tekton, whereas Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager and SaltStack. See our Bamboo vs. Chef 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.