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 big things that made us choose Bamboo, is it seamlessly integrates its APIs into NetSuite, which is our main ELP system."
"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."
"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."
"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 my experience Bamboo is scalable."
"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."
"It has been very easy to tie it into our build and deploy automation for production release work, etc. All the Chef pieces more or less run themselves."
"This solution has improved my organization in the way that deployment has become very quick and orchestration is easy. If we have thousands of servers we can easily deploy in a small amount of time. We can deploy the applications or any kind of announcements in much less time."
"Stable and scalable configuration management and automation tool. Installing it is easy. Its most valuable feature is its compliance, e.g. it's very good."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"The scalability of the product is quite nice."
"One thing that we've been able to do is a tiered permission model, allowing developers and their managers to perform their own operations in lower environments. This means a manager can go in and make changes to a whole environment, whereas a developer with less access may only be able to change individual components or be able to upgrade the version for software that they have control over."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"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 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."
"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."
"It would be great if Bamboo could introduce a more containerized deployment model."
"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’s technical support services, in terms of speed of response, need improvement."
"It's a little outdated. It's three years old."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"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."
"The agent on the server sometimes acts finicky."
"The solution could improve in managing role-based access. This would be helpful."
"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."
"It is an old technology."
"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 13th 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 "Useful for large infrastructure, reliable, but steep learning cureve". 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 BigFix. 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.
