Bamboo Reviews

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.

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.

Bamboo is a CI/CD tool for low-cost teams in my company. Some of my company's customers come to us with a certain level of comfort they experience, and we help them continue with that.

The most valuable feature of Bamboo is that it is a good tool for CI/CD integration. Bamboo is not a tool like Jira, which is mostly a ticketing system.

People know more about Jira than Bamboo. In general, people should know that Jira and Bamboo are similar solutions. The marketing strategy of Bamboo is an area of concern where improvements are needed.

I believe that Bamboo should provide some support as there are too many scripts when we try to do something in GitHub. Every tool has its own style of automation, which is something I would like to be standardized so that the tools become more friendly when it comes to porting so that I can use Bamboo or GitHub Actions freely. I want all the tools to have the same standards, which would help our company.

I feel there is always a scope for improvement in the product's initial setup phase.

Bamboo should provide a permanent free tier, not a time-bound one for startups, as it helps users know if something works well and is utilized or not. Bamboo should offer some permanent free trial for one user or ten users, whatever it is.

I have been using Bamboo for almost eighteen months.

Most of the time, our scripts were bad. There were also some memory issues and delays around building scripts. My company could handle script issues since most of them were because of the problems at our end. Apart from the aforementioned area, we found no issues with the product.

My company has been happy with Bamboo's scalability options, especially considering that more developers have joined my company.

Scalability-wise, I rate the solution a seven to eight out of ten.

One of my company's clients has 15 users of the solution.

The solution's technical support is good since my company hasn't had any issues with them. My company's interaction with Jira's support was more compared to Bamboo. My company doesn't have issues with Bamboo's quality or response time. Most of the time, my company interacted via Bamboo's online forums, and we used to get answers.

My company can be described as a diverse company, so we use what our customers use. I have experience with Bitbucket, CircleCI, and GitHub.

The product's initial setup phase is okay for us since our company is an expert in it.

The solution is deployed on the cloud.

For those who have a suite from Atlassian, my company would prefer them to use Bamboo. My company doesn't want our clients opting for one tool for CI and another tool for ticketing. Generally, we prefer to go with the corresponding solutions offered by a vendor. GitHub is always good, but it is limited as it is a free tool.

Bamboo should offer products for free to startups or the first ten users, rather than just thirty days, an approach through which it can hook people. There should always be a free tier of products, and as Bamboo grows, I think its costs would be nothing, considering the value it gives users.

I never heard about Bamboo in the past as much as Jira or Confluence. I came to know of Bamboo through meetings or emails in my company with our customers. It doesn't seem like Bamboo is digitally marketed very well. With DevOps becoming popular, products like Bamboo have so much to offer.

I rate the overall tool 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.

• 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.

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.