Try our new research platform with insights from 80,000+ expert users

Bamboo vs Chef comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Bamboo
Ranking in Build Automation
6th
Average Rating
7.4
Number of Reviews
22
Ranking in other categories
No ranking in other categories
Chef
Ranking in Build Automation
17th
Average Rating
8.0
Reviews Sentiment
7.9
Number of Reviews
19
Ranking in other categories
Release Automation (6th), Configuration Management (17th)
 

Mindshare comparison

As of December 2024, in the Build Automation category, the mindshare of Bamboo is 8.7%, down from 8.9% compared to the previous year. The mindshare of Chef is 0.4%, down from 0.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Andrea Carella - PeerSpot reviewer
High availability, helpful support, and plenty of plugins available
I have used Google Cloud Platform and Amazon AWS for implementing Bamboo. It is not difficult to complete. The length of time it takes for deployment depends on a lot of variables, such as how the pipeline is deployed and what type of infrastructure is present. However, it typically takes only hours not days. I rate the setup of Bamboo a nine out of ten.
Arun S . - PeerSpot reviewer
Useful for large infrastructure, reliable, but steep learning cureve
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 solution is good to manage multiple large infrastructures. We can have 10 to 10,000 users using this solution and it manages them well.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"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 tool is useful for continuous deployment."
"Bamboo was used extensively in our organization for PCA compliance."
"The most valuable features are compiling and deployment."
"The most valuable feature of Bamboo is that it is a good tool for CI/CD integration."
"It can do the CI pipeline well."
"In my experience Bamboo is scalable."
"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."
"I wanted to monitor a hybrid cloud environment, one using AWS and Azure. If I have to provision/orchestrate between multiple cloud platforms, I can use Chef as a one-stop solution, to broker between those cloud platforms and orchestrate around them, rather than going directly into each of the cloud-vendors' consoles."
"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 is a well thought out product which integrates well with what developers and customers are looking for."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"Deployment has become quick and orchestration is now easy."
"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."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"The most valuable feature is the language that it uses: Ruby."
 

Cons

"Bamboo’s technical support services, in terms of speed of response, need improvement."
"The performance around the deployment feature could be improved."
"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 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 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."
"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."
"It's a little outdated. It's three years old."
"It would be great if Bamboo could introduce a more containerized deployment model."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"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."
"I would like to see more security features for Chef and more automation."
"The agent on the server sometimes acts finicky."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"The solution could improve in managing role-based access. This would be helpful."
"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."
 

Pricing and Cost Advice

"I rate the solution's pricing a three out of five."
"The price of Bamboo is reasonable."
"The server products for small teams used to offer excellent pricing. However, Atlassian has since changed the offering and the pricing is more expensive. I do still think the solution offers good value for money."
"There is a subscription required to use Bamboo."
"I rate the product’s pricing a five out of ten."
"If Bamboo could provide more flexibility on pricing, that would help. On the agent side, if you want to increase the number of agents it should be less expensive. If they can provide some better pricing model, it will help, whether we are going to use it or are already using it."
"Pricing for Chef is high."
"The price is always a problem. It is high. There is room for improvement. I do like purchasing on the AWS Marketplace, but I would like the ability to negotiate and have some flexibility in the pricing on it."
"Chef is priced based on the number of nodes."
"The price per node is a little weird. It doesn't scale along with your organization. If you're truly utilizing Chef to its fullest, then the number of nodes which are being utilized in any particular day might scale or change based on your Auto Scaling groups. How do you keep track of that or audit it? Then, how do you appropriately license it? It's difficult."
"We are using the free, open source version of the software, which we are happy with at this time."
"Purchasing the solution from AWS Marketplace was a good experience. AWS's pricing is pretty in line with the product's regular pricing. Though instance-wise, AWS is not the cheapest in the market."
"I wasn't involved in the purchasing, but I am pretty sure that we are happy with the current pricing and licensing since it never comes up."
"We are able to save in development time, deployment time, and it makes it easier to manage the environments."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
823,875 professionals have used our research since 2012.
 

Comparison Review

it_user217035 - PeerSpot reviewer
May 27, 2015
Bamboo vs. Jenkins
A biased and subjective comparison of Bamboo and Jenkins as CI servers for mobile development, based on practical experience with both. Continuous Integration and Continuous Deployment (Delivery, Distribution) has been around for quite a while. But surprisingly enough on a global scale it pretty…
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Manufacturing Company
15%
Computer Software Company
12%
Government
9%
Financial Services Firm
23%
Computer Software Company
15%
Manufacturing Company
6%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Bamboo?
Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process.
What needs improvement with Bamboo?
Integrating workflows with other platforms can be challenging. The capabilities of these platforms sometimes fall short compared to others. Initially, it was difficult for us because the plugins we...
What do you like most about Chef?
Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code.
What needs improvement with Chef?
Chef does not support the containerized things of Chef products. In the future, Chef could develop a docker container or docker images.
 

Comparisons

 

Learn More

 

Overview

 

Sample Customers

Neocleus, MuleSoft, Interspire
Facebook, Standard Bank, GE Capital, Nordstrom, Optum, Barclays, IGN, General Motors, Scholastic, Riot Games, NCR, Gap
Find out what your peers are saying about Bamboo vs. Chef and other solutions. Updated: December 2024.
823,875 professionals have used our research since 2012.