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."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."
"The most valuable features are compiling and deployment."
"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."
"The platform helps us with automated and timely backup. It provides data replication as well."
"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 feature of Bamboo is that it is a good tool for CI/CD integration."
"It can do the CI pipeline well."
"Bamboo was used extensively in our organization for PCA compliance."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"The product is useful for automating processes."
"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."
"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."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"Deployment has become quick and orchestration is now easy."
"Chef recipes are easy to write and move across different servers and environments."
"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 would be great if Bamboo could introduce a more containerized deployment model."
"It can be challenging for someone new to the system or ecosystem to grasp, making it difficult to train new people and help them understand."
"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."
"Bamboo’s technical support services, in terms of speed of response, need improvement."
"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."
"If they can improve their software to support Docker containers, it would be for the best."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"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."
"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."
"Since we are heading to IoT, this product should consider anything related to this."
"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."
"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.
