Bamboo Reviews

We use Bamboo to maintain the sales process and ensure continuous integration. This involves integration with Bitbucket as the deployment server.

Some of my recent projects have been built on a microservices architecture that utilizes microservices. This stream works, running a big e-commerce solution, and is containerized. Bamboo has helped us to make this process perfect by reducing the risk of failures on production deployments, making the changes deployed into production much smaller, thereby reducing errors and easing the sign-up process for the release itself. It generally makes the solution flexible and helps maintain information about what has been deployed and what hasn't. It's much easier to manage. Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process.

Bamboo allows for any customization made. It provides tools to configure the process as much as you need and want. Then, it helps to run big IT projects, scale them as much as you need, and utilize the process that the client is used to.

The tools and capabilities of the system are extensive. It can be challenging for someone new to the system or ecosystem to grasp, making it difficult to train new people and help them understand.

I have been using Bamboo for ten years.

The stability of the solution is good.

The solution’s scalability is excellent. Around 200-500 users are using this solution.

I would rate the solution’s scalability a ten out of ten.

There is quite a large community around Atlassian's Bamboo. Most issues can be solved by browsing through the documentation or forums. Almost every problem you encounter has likely been experienced by someone else in the past, and with such a large community, finding solutions is generally straightforward.

Atlassian has an advanced approach to solving issues. If it's very systematic, you can always stay updated about the resolution of the problem.

We've never really utilized different tools extensively. Bamboo works efficiently from a management perspective. If you need to inform a developer to deploy a particular version, it handles this task seamlessly. Any potential miscommunication or oversight is mitigated using Bamboo, provided it's correctly configured. It automatically provides the necessary information without excessive emails or phone calls to confirm whether something has been deployed.

It's crucial to understand the business process and operations of the client thoroughly. Ultimately, deploying the software aims to fulfill the needs of the business itself. No tool can effectively handle that volume without understanding how the business operates, its expectations, and its processes regarding deploying software into production. Everything begins with understanding the client's business or the business purpose behind the configuration of Bamboo and essentially any step within the development process. Once you grasp this understanding, you can configure Bamboo properly, leveraging its capabilities to support various business processes, which is commendable.

The configuration possibilities are pretty endless. It provides space for fewer issues you may experience due to misconfiguration. Any problems are not about the system itself but rather misconfiguration, which can sometimes be hard to identify. The components you wish to deploy haven't been deployed for some reason, and then you must determine why it didn't happen. 

Overall, I would rate the solution an eight out of ten.

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.

I implement this solution for clients.

The primary function of Bamboo is to facilitate the creation of a CI/CD pipeline, which is the main use case for the tool. Its main purpose is to automate the pipeline, enabling a DevOps approach for both the client and the company.

One of the significant benefits of Bamboo is its built-in support for numerous clients and the ability to tailor its capabilities to your specific requirements. This high level of customization enables you to create pipelines that are ideally suited to your needs, making it an invaluable tool for conducting advanced testing.

The marketplace offers a wide range of pre-tested connectors that are readily available for use in your builds. However, if you cannot find a suitable connector, Bamboo also supports the integration of APIs, allowing you to seamlessly incorporate custom solutions into your system.

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.

Currently, Atlassian University does not offer a dedicated course for learning Bamboo. If you wish to embark on a learning journey to acquire knowledge about the solution, your only recourse is to seek out experienced users who are willing to share their expertise on learning platforms like LinkedIn or Udemy. However, this falls short of a structured classroom-based approach, which Atlassian should consider incorporating into their official university platform to provide a comprehensive learning experience for users. However, there is a lot of documentation, but this is not the same as training.

This lack of training might be due to the focus that Atlassian has on the cloud platform rather than on-premise.

I have been using Bamboo for a couple of years.

Bamboo is highly stable, as long as the compatibility and upgrades of relevant libraries and dependencies remain untouched. It can become problematic if upgrades or updates are made to dependent libraries or other software. If, for example, Java is updated to an unsupported version, this needs to be communicated clearly to the customer. Such updates usually fall under the purview of security and operations teams, who check for patches and other necessary updates. These factors can have a significant impact on performance. However, overall, Bamboo performs very well and is highly robust.

I rate the stability of Bamboo an eight out of ten.

Bamboo is scalable and it is easy to do. Theoretically, you can add as many nodes as you want. You don't need to incur additional licenses for the additional nodes added which is a large benefit.

We have clients that are small to large-scale enterprises. However, most of our clients are enterprise-sized, such as government entities. Approximately 40 percent of our clients are SMBs and 60 percent are enterprises.

I rate the scalability of Bamboo a nine out of ten.

Improvement in Bamboo support is needed, particularly regarding security-related inquiries. Responses to security questionnaires required by the customer's security team are often delayed. However, regarding technical support, their responsiveness is generally good, depending on the severity of the issue. They can also provide direct support sessions when necessary. Nevertheless, our experiences vary when it comes to security, particularly from the PC side, where we typically face delays in obtaining answers to questionnaires provided by the customer's security team.

I rate the support from Bamboo a six out of ten.

Neutral

The complexity of implementing Bamboo varies based on the client's specific needs. Installing and obtaining basic information is simple, but building a pipeline can be more challenging. This task is typically handled by a DevOps engineer.

Unless requested by the client, the implementation would not be handled by the partner, which can be quite challenging. 

The installation and configuration can be straightforward. 

Excluding the pipeline, the full implementation can be done in two days.

Typically, the implementation process involves setting up the infrastructure and ensuring that all prerequisites are met, including the necessary platforms and versions compatible with Bamboo. The deployment complexity varies depending on whether it's done on Linux or Microsoft Windows OS. The deployment process on Microsoft Windows OS is relatively straightforward, requiring the installation of prerequisites and a supported DB server. If deployed on a PC, a shared network folder with the appropriate security access is also necessary. These steps are well-documented, making them easy to follow. Therefore, deployment is not overly challenging. However, configuring the system from within can be more complicated.

I rate the initial setup from Bamboo a seven out of ten.

My advice is that if you intend to implement Bamboo, you should consider it as part of a complete DevOps solution. You must think about the other applications natively integrated with it, such as Jira, JSM, and Bitbucket. Bamboo's true power is realized when it is combined with these other solutions from the Atlassian suite. In this way, you can achieve much better value.

I rate Bamboo an eight out of ten.

I provided my rating of Bamboo based on its strong scalability and overall quality. While its support could be better, its performance is quite robust. However, there is a learning curve to understand how to set it up, making it challenging for new users. Nevertheless, for experienced DevOps engineers, it is pretty straightforward to set up.

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.

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.