Bamboo Reviews

Bamboo is used for different Java and Angular applications.

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.

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.

I have been using Bamboo for approximately five years.

Bamboo has been stable in our experience.

The solution is scalable.

We have approximately 15 people using this solution in my organization.

We have escalated some questions to the Atlassian support team. They have a good team for support.

I would rate the technical support of Bamboo a four out of five.

If we compare the initial setup of Bamboo's with Jenkins, Jenkins's setup is easier. Bamboo comes with more configuration when you start setting it up. However, Bamboo is more of an enterprise tool as compared to Jenkins because it supports different databases. You can configure Bamboo with MySQL, Oracle, or any database. This is why the setup, requires more configuration, but the setup is straightforward. It is not that complex, once a person has done it they become aware of it and can do it again with less trouble.

We did the implementation of the solution ourselves.

We have a team that does the maintenance of the solution.

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.

We have a standard license to use the solution. There can be some additional cost if we use some commercial plugins.

I have evaluated other solutions such as, Jenkins.

I rate Bamboo an eight out of ten.

Bamboo is an automation tool.

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.

I have been using Bamboo for approximately eight months.

Bamboo has been stable.

In my experience Bamboo is scalable.

I work for an insurance company and our whole company uses Bamboo.

The technical support provided by Atlassian is very good.

I have previously used Gitlab.

There is a subscription required to use Bamboo.

I would recommend this solution to others.

I rate Bamboo an eight out of ten.

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 are using Bamboo for CICD, where you need to build Java architect and boot application architect. Then, we deploy that into some Comcast web servers. Bamboo was used extensively in our organization for PCA compliance.

It would be great if Bamboo could introduce a more containerized deployment model. Bamboo should also provide more user-friendly flexibility. For example, if we want to maintain the Bamboo job configuration, we need to export the configuration to Java. However, it would be good if the coding syntax could be simplified.

I have been using Bamboo for one and a half years.

I rate Bamboo a seven out of ten for stability.

I rate Bamboo a seven out of ten for scalability.

Overall, I rate Bamboo a seven out of ten.

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.