Bamboo Overview

Bamboo is the #5 ranked solution in our list of top Build Automation tools. It is most often compared to Harness: Bamboo vs Harness

What is Bamboo?
Bamboo is a continuous integration and delivery tool that ties automated builds, tests and releases together in a single workflow. It works great alongside JIRA and Stash providing a fully traceable deployment pipeline.
Buyer's Guide

Download the Build Automation Buyer's Guide including reviews and more. Updated: June 2021

Bamboo Customers
Neocleus, MuleSoft, Interspire
Bamboo Video

Filter Archived Reviews (More than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
ITCS user
Solution Management at a computer software company with 51-200 employees
Vendor
PRO: flexibility when setting up our builds. CON: lacks support for branched builds using multiple source repositories

What other advice do I have?

Plan before you start, Bamboo is 'only' that which automates. One should have a decent design of how the build needs to work internally and have that (scripts, servers, descriptors ...) in order before attempting to automate on a large scale. Secondly, don't be afraid to change things to you application or pipeline to help the automation to be more efficient - for example we replaced massive chunks of hard SQL from the build scripts by a webservice to avoid dependencies to JDBC in our builds.
ITCS user
Senior Build & Release Engineer at a non-tech company with 501-1,000 employees
Vendor
The REST API for our deployment project is still very basic, but with Bamboo, we've been able to implement an on-demand, push-button release strategy.

What other advice do I have?

Make sure you don't become dependent on the tool for basic delivery of software. And this goes for any tool you use for automating the building and deploying of your apps. Meaning, if Bamboo were to go down for whatever reason, you want to make sure you can still build and deploy software. To avoid Bamboo becoming a single point of failure, have all of your script tasks run a file that is managed in a repository instead of writing it in line in Bamboo.
Find out what your peers are saying about Atlassian, Jenkins, JetBrains and others in Build Automation. Updated: June 2021.
511,307 professionals have used our research since 2012.
ITCS user
Software Development Consultant at a financial services firm with 1,001-5,000 employees
Vendor
There are some stability issues with Java 6, but it offers build agents for Windows and Linux.

What other advice do I have?

It's dependent on how many build teams you have. For small development sites, Hudson or Jenkins will suffice, I think. Because we’re building our main applications in-house, we always choose supported and licensed tools.
ITCS user
Lead Release Engineer at a tech vendor with 51-200 employees
Vendor
Bamboo easily integrates into an Atlassian stack.

What other advice do I have?

Pros: - Integrates well with Atlassian products - Nice Modern Interface Cons: - Agents are limited by the license - No method to provide version control for Build Plans - It's expensive - Most plugins cost $$$ Personally I'm in the process of moving away from Bamboo. Sure it looks nice, but I need flexibility. If you plan on creating a build server for each of your teams or projects, don't use Bamboo and use Jenkins instead. It has a richer plugin base, no limit on agents, and allows version control of plans and configuration easily. It's also open source software so the cost is much lower…
ITCS user
Software Configuration Manager at a marketing services firm
Real User
The new Salesforce plugin looked interesting despite the fact you had limited control on how the SF package is deployed.

What other advice do I have?

While the community may grow over time, please ensure your current/future processes are not hindered by Bamboo's faults. Bamboo is likely to improve with time, it may be advisable to use a different solution until the product grows a bit more mature.
it_user185772
Senior Software Architect with 5,001-10,000 employees
Vendor
Jenkins vs. Bamboo vs. Travis
This is the first article of the Continuous Integration, Delivery and Deployment series. We’ll start out journey with brief explanation of Continuous Delivery. After short exploration of some of the tools used today, we’ll move towards the flow (from setting up brand new environment and getting the code from the repository to the creation of fully tested and verified distribution). Each section will present different approaches, compare different tools and, finally, provide some hand-on examples. After the flow, we’ll explore changes required in the development life cycle. Finally, we’ll dive into last steps required for the transition from Continuous Integration towards Continuous Delivery and Deployment. “Legacy code is code without tests” – Michael Feathers According to Martin…
ITCS user
Build and Release Engineer at a tech vendor with 201-500 employees
Real User
APIs were helpful for creating customizations but there are limited options with SSH plugins

What other advice do I have?

If you are looking for good integration with Atlassian products and then this is the tool.
Product Categories
Build Automation
Buyer's Guide
Download our free Build Automation Report and find out what your peers are saying about Atlassian, Jenkins, JetBrains, and more!
Quick Links