Bamboo Reviews

We are using it to push and pull containers and other data via CI/CD pipeline.

It didn't help me as such. It was just a part of the project.

It can do the CI pipeline well.

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.

I have been using this solution for three months.

It has a steep learning curve, but it is fairly stable.

Based on my understanding, it is scalable.

There is limited technical support.

Its initial setup is complex.

We have a separate team that takes care of it.

I am not completely satisfied with this solution. It performs one function well, but it requires so much integration. I would advise others to use a better-integrated system rather than Bamboo. We'll be moving to XebiaLabs, now known as Digital.ai, for production and other environments. XebiaLabs is a bit better than Bamboo in some aspects.

I would rate Bamboo a six out of ten. It is okay to use, but there is a lot of room for improvement.

We use Bamboo as our continuous integration server.

We have a project based on AWS and Java, and Bamboo is the solution that fit our needs.

The most valuable features are compiling and deployment.

The performance around the deployment feature could be improved.

We have been using Bamboo for three years.

We have experienced a couple of crashes, which is why we have upgraded to new versions as they are released. It seems now that everything is okay. We have 70 people who use this solution, most of which are developers using it for compilation. There are two or three system integrators.

In the context of our project, scalability is enough for our purposes.

I have not personally been in touch with technical support. One of my colleagues may have been, but I haven't heard any feedback.

The initial setup was a lovely experience for us because the first time we tried it, it was ok.

We did not evaluate other options because we primarily use Microsoft development technology and we have only a few targets that are not supported. We had done some research and found the Microsoft Azure DevOps VSTS was not competent enough to support Core Java lambda functions, so we picked up Atlassian Bamboo and we are happy with it.

Bamboo is a solution that I recommend, especially for open-source development organizations that use all open-source tools. Atlassian suite is the best partner for such organizations.

I would rate this solution an eight out of ten.

This is a part of the CI/CD. We use this tool to move into production. 

It does automation which saves time so that people don't have to waste time. We save around 20% on time. 

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. 

It doesn't take up other resources. It's very efficient. 

It's a little outdated. It's three years old. 

I have only used Bamboo at my current company and I've been there for a year now. 

It is very stable. We have experienced issues but there is alway support.

We are upgrading to the latest version because of the scalability. 

I usually solve any problems we have by myself. If for whatever reason there isn't any information available online we contact their support and they get back to us within hours. I opened around five to ten tickets with them. 

They have very stable pricing. The license is 120,000 per year for the license and maintenance.

I would rate it an eight out of ten. Not a ten because the GUI is old I always have to find the right plugin.

My advice to someone considering this solution is that if you have the money, buy it. 

I find the solution quite easy to use. 

One of the big things that made us choose Bamboo, is it seamlessly integrates its APIs into NetSuite, which is our main ELP system.

The fact that it's integrated within Oracle products, and that it can be managing statutory people in our organization, and the features and functionality are all huge selling points. 

We felt Bamboo was a simple overall tool, and that it was also cheaper than Oracle's products at the time, which is why we chose it.

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.

I've been using the solution for about a year.

The solution is pretty stable.

The solution is scalable. We have about 400+ users on it currently. We use it on a daily basis, but I don't know if we plan to increase usage at this time.

We have our own in-house team that helps troubleshoot any issues we might have. If they can't resolve it, they may go to the Bamboo help desk.

I wasn't really involved in the implementation process so I can't really comment on it. 

We have two administrators on the solution currently.

We use the cloud deployment model.

I'd recommend that solution. Everything structure and systems-wise is quite customizable.

I'd rate the solution eight out of ten.

We are very fond of the flexibility it offers in terms of setting up our builds. We have a wide variety of components we need to build which often require custom actions or manipulations using in house technology. Bamboo allows us to set this up quite easily by the flexible configuration features it includes.

Secondly we really like the integration of the build aspect and deploy aspect. One of the recent major releases included this feature to link build and deploy projects together allowing a deployment pipe-line to be setup completely in Bamboo. This makes the status of deployments very visible and also allows for easy follow up and even rollback in case a deployment causes too much havoc.

Thanks to Bamboo we are able to build changes made by development quite quickly and allow them to deploy to our internal environments when needed (as well as automated during the night). This significantly reduces the effort required to get something into test.

The fact that all builds use a unified setup and infrastructure makes it much easier to control and adapt the ever increasing number of builds.

We are lacking proper support for branched builds using multiple source repositories. The current approach is quite clunky (or non-existent) but it seems there is something in the pipe line for the end of the year according to a recent post on the Bamboo Jira.

We have been using Bamboo for about 6 years now

Not at all, over all those years we only had a handful of issues and that's probably because we always take each new update directly.

No, we never encountered any serious regression. For the few cases we encountered bugs they were fixed in a reasonable time interval.

Scaling out a build system is not always easy, but thanks to the remote agent technology we are able to scale out and add nodes in a transparent way.

We use a 3d party for our license management, which makes it hard to judge this but we never had direct interactions with Atlassian Customer support.

Pretty good once you get trough the initial levels of the support team, it can take a while before you are able to prove that there's a genuine issue.

We came from Jenkins back in the day, I recall our most important reasons to switch where the enterprise readiness of Bamboo and its integration in the Atlassian stack (Jira and others).

Bamboo is very easy to deploy, all it takes is extracting the distribution and a JRE to run it. This also goes for the remote agents which install by running a JAR which already contains the configuration for communicating with its master.

We implemented in house.

That would be 100%, the time saved in development is enormous.

We started out using only a number of agents and moved to a bigger setup using many remote agents over the years. The cost depends on the agents used and amount of boxes deployed to run them on.

Only Jenkins, see previous answer.

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.

The Deployment Project

Bamboo, along with its integrated deployment and release pipeline, enabled us to go from a monolithic, once a month release cycle, with many post-release incidents to an on-demand, push-button release strategy where we deployed over 200 times a month with very few to no release-related incidents.

Using this tool, we were able to empower the dev teams to push their own changes to production rather than rely on the operations or release teams to release it.

The REST API for our deployment project is still very basic and lacks the ability to provide a decent amount of custom automation. For many things, we had to resort to direct database queries simply because certain data was not exposed via the API.

I've used it for five years.

No issues encountered.

Every once in a while deployments would hang and we weren't able to clear them without restarting the service. It didn't happen a lot and it may have been due to how we configured the app on the server.

Not really. As long as your organization is willing to pay a bit more, Bamboo can scale to meet your needs.

7/10 - sometimes you just want to talk to someone over the phone, but this isn't very easy with Atlassian. They have a ticket support system that's pretty good at connecting you with a customer service rep, but sometimes this means you have to go back and forth, waiting for the representative to reply on the issue in order to isolate a problem.

7/10 - sometimes you just want to talk to someone over the phone, bu this isn't very easy with Atlassian. They have a ticket support system that's pretty good at connecting you with a customer service rep, but sometimes this means you have to go back and forth, waiting for the representative to reply on the issue in order to isolate a problem.

Bamboo was already being used.

It was pretty straightforward. Atlassian standardizes setup across products for the most part, so it was easy for us to install, configure, and navigate.

We implemented it ourselves in-house.

We got a ton of product and development time back across the board, which could be translated to several tens of thousands of dollars.

Keep in mind that Bamboo pricing is based on number of remote agents. Agents are what you used to load balance build and deployment tasks, so depending on how large your development shop is, what your software architecture looks like, and how often you intend to build and deploy new versions of software, it can get fairly pricey to support a higher volume pipeline.

We evaluated Jenkins and Thoughtworks Go. At the end of the day, Bamboo just integrated better with the other tools we were already using - JIRA, Stash, Confluence - and provided better push button deployment control. Bamboo provided such a seamless delivery pipeline and visibility to all stakeholders through its easy integrations with our already existing toolset.

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.

• Multiple build agents for both Windows and Linux
• Automatic branch building - same build plan for trunk and branches
• Connections with other Atlassian tools - JIRA and FishEye/Crucible

We have many developer teams building in Java, especially our Continuous Integration team. Bamboo has proven its value for the teams.

There are no areas that need improvement.

I've used it for seven years,

No issues encountered.

Once, with Java 6, there were some issues, but thanks to information from Atlassian support we changed to Java 7 and it works fine.

No issues encountered.

I'm satisfied, 8/10.

I'm satisfied, 8/10.

We used CruiseControl, and we switched because of better functionality in Bamboo.

It was straightforward, as the default agent and remote agents install out-of-the-box. Only some memory tuning was needed.

We did it in-house.

It's hard to say, the yearly license/support/maintenance costs are low in relation to the added functionality.

I see no problem in paying for support, especially because licensing is remote agent based.

• CruiseControl
• Hudson

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.

Ability to interface easily with other Atlassian applications.

It allows a controlled process in which to build software.

Version control for plans is currently not really possible. This is pretty much the deal breaker for me and why I'm moving away from Bamboo.

The Upgrade process is also clumsy and requires manual steps. I'm not a fan of tarballs.

3 years.

You may need to upgrade in steps if you are upgrading a relatively old version.

At one time we used to have issues with system stability. You may need to tinker with your systems heap settings.

You are limited by the number of agents you are willing to buy. This means all your teams end up building on the same agents or worse, the master itself.

This is the second deal breaker for me and why I'm currently advocating to move to a different build system.

Atlassian support is usually pretty good in my experience.

They need to work on their upgrade paths and deployments. If you fall to a few versions behind you may end up doing a multi-version installation. Not fun.

The license is the worst. It costs the most. In addition to that we run it on a very beefy server (HP DL360 G8 with 24G of ram). I would not run this software on subpar hardware.

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. Maintaining Bamboo is also a chore, not so with Jenkins which is distributed as a RPM, DEB, and now Docker container. Bamboo I'm still stuck downloading a tarball.