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."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 feature of Bamboo is that it is a good tool for CI/CD integration."
"One of the big things that made us choose Bamboo, is it seamlessly integrates its APIs into NetSuite, which is our main ELP system."
"It can do the CI pipeline well."
"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 features are compiling and deployment."
"We have had less production issues since using Chef to automate our provisioning."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"Chef can be scaled as needed. The Chef server itself can scale but it depends on the available resources. You can upgrade specific resources to meet the demand. Similarly, with clients, you can add as many clients as you need. Again, this depends on the server resources. If the server has enough resources, it can handle the number of servers required to manage the infrastructure. Chef can be scaled to meet the needs of the infrastructure being managed."
"The product is useful for automating processes."
"The scalability of the product is quite nice."
"Deployment has become quick and orchestration is now easy."
"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 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."
"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'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."
"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."
"In the future, Chef could develop a docker container or docker images."
"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."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"If they can improve their software to support Docker containers, it would be for the best."
"Since we are heading to IoT, this product should consider anything related to this."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"The solution could improve in managing role-based access. This would be helpful."
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 "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 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.