Bamboo Reviews

My current use case for Bamboo is not as active as it once was. The team that I worked for still uses it, but I don't work on it as much anymore. Basically, Bamboo is used for CI/CD pipelines to build projects and deploy them. That's the main use of it.

The last time I worked with Bamboo was still sometime in the present, as I still work with it now and then. I am not as active as in the past. I still help some of the team members occasionally when needed. Day to day, I don't use it so much anymore. I stopped using it when I stopped doing work for that area, which was around the beginning of this year.

The most useful features in Bamboo for my team are the build automations and deployments. That's the main capability.

The reports part in Bamboo is useful, but it depends on what plugins you use. You can enable certain plugins to get reporting on code quality and all of that. The reporting is good for that.

Bamboo integrates well with Jira and Bitbucket. Bamboo integrates with Bitbucket seamlessly, and that's your Git repository. The integration into Jira is also seamless. Jira gives you a nice view of tasks loaded and how it links to the code and everything. That whole integration is very streamlined.

The main benefits Bamboo provides for me and my team are the automation to pick up code changes and automate the deployments, building images. The automation is really the big benefit for the CI/CD pipeline.

Regarding improvements for Bamboo, I can't think of anything right now. Bamboo is serving the purpose that we needed it for.

I would say pipelines for model building could be an area of focus. However, I can't really comment on that because I haven't looked at Bamboo to assist with machine learning pipelines. If they haven't focused on building MLOps pipelines, that's definitely an area where they could assist businesses. I haven't looked at what Bamboo offers for MLOps, so it's possible that they've already built in features. Machine learning and AI are in big demand at the moment. If they haven't focused too much on MLOps, that's probably where they can improve.

I have been working with Bamboo for seven years.

I would rate the stability for Bamboo an eight from one to ten.

From my personal experience regarding scalability and the ability to scale, I find that sometimes the agents run out of resources and then it takes quite a while to get additional infrastructure. Although Bamboo can scale and you can add more agents, sometimes it's just a bit of a problem. That's why cloud solutions are becoming more popular because those things are very much automated. If you need more agents, you just switch on more agents. If it's self-hosted and you haven't planned for spinning up a lot of agents, you're going to get stuck.

I can't really rate technical support from Atlassian from one to ten because the teams that I worked with have specialized teams that look after Atlassian products within the organization. Those teams get the support from Atlassian, so I can't really comment on it because we normally just interact with those teams who look after the platforms.

I don't directly work with Atlassian as my company does not purchase the product directly from the vendor. It is more the customers that we work with that purchase directly from them.

The initial setup process for Bamboo was pretty straightforward when I looked at it a long time ago. However, many of the teams that I work with now are looking at cloud options. Whether it's complex to set up, I think fewer and fewer people are going to host their own versions and set up their own versions. In summary, when I did my own setup with Bamboo long ago, it was straightforward and not too difficult. Even if they make it simple, I think people are going to look more at cloud-hosted options so they don't worry about setting up and hosting themselves.

Microsoft DevOps is probably the alternative I can compare Bamboo with.

I wouldn't say I switched from Bamboo to DevOps. It's just that I work with both. It depends on what the customer adopts. From my perspective, I need to be able to work with both because it depends on what the customer prefers. I wouldn't say switch. I would say it's more a matter of working with both because in some instances, we'll work with one and in other instances with the other.

The term multi-stage building plans in Bamboo doesn't really ring a bell for me. I just use the standard features. I would rate my overall experience with Bamboo an eight out of ten.

Bamboo is a continuous deployment tool by Atlassian.

The tool is useful for continuous deployment.

The capabilities to use YAML must be improved. The tool is not capable of using YAML efficiently.

Since the tool depends on Jira, the stability is somewhat degraded. I rate the stability a seven out of ten. The stability must be improved.

The tool is deployed on-premise. So, the scalability depends on the resources we allocate on-premise. We have four users in our organization.

The setup is moderately difficult. It is not highly complicated, but it is not easy. We must go through some steps to complete the implementation. Once the product is implemented, it will be stable. We face some challenges since the tool is deployed on-premise. The capabilities are adequate for our needs, though.

Bitbucket can be used for cloud solutions.

If we are upgrading CI/CD from on-premise, we would need Bitbucket and Bamboo. Atlassian products rely on Jira. Bitbucket and Bamboo are integrated with Jira on-premise. I will recommend the product, but not very strongly. The solution does not have AI features.

Continuous deployment is an enormous part of the software development cycle. Bamboo is a suitable solution for on-premise deployments. However, there are other alternatives available in the market. Overall, I rate the product a seven 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 use Bamboo for data replication, backup, and recovery.

The platform helps us with automated and timely backup. It provides data replication as well.

The product’s most valuable feature is its ability to work with VMware and Hyper-V.

Bamboo’s technical support services, in terms of speed of response, need improvement. They should work on providing faster backup replication as well.

We have been using Bamboo for almost a year.

The product could be more stable. I rate its stability five out of ten.

I rate Bamboo’s scalability a six out of ten. It doesn’t work well in all environments. It has some drawbacks and challenges. Also, fixing them takes a long time due to the technical support team's slow response time.

The technical support services could be better.

Neutral

I have used Veeam and NetApp before.

The initial setup is easy. I rate the process an eight out of ten.

I rate the product’s pricing a five out of ten.

I rate Bamboo a six out of ten. It suits small and medium businesses with brand-new servers, up-to-date operating systems, and good network switches. I would not recommend it for large organizations.

We utilize Bamboo to automatically deploy multiple applications that manage various aspects of our department across several environments, including testing and production. By employing the same pipeline for each application, we can effectively manage and automate the process. As a result, we've pursued Kubernetes training to develop scalable applications.

I have worked on both on-premise and cloud deployments of Bamboo.

The most valuable features of Bamboo are its performance and UI. Additionally, there are a lot of useful plugins, integration with other solutions, such as Bitbucket and Jira, and a helpful online community.

Bamboo could improve by having compatibility with GitLab. It would be better to have this platform for deploying code and storing container registries. Bamboo does not have a container registry. Additionally, there could be more features added.

I have been using Bamboo for approximately three years.

The stability of Bamboo is excellent.

I rate the stable of Bamboo a ten out of ten.

I worked on a project which had 2,000 developers using the solution.

The solution is best suited for enterprise companies.

The solution is scalable.

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

The support for Bamboo is great. They have been helpful and they provide a high-level service. Additionally, they are quick to respond.

Positive

I have used Jenkins and I found that Bamboo is more powerful and easier to use. 

I have used Google Cloud Platform and Amazon AWS for implementing Bamboo. It is not difficult to complete.

The length of time it takes for deployment depends on a lot of variables, such as how the pipeline is deployed and what type of infrastructure is present. However, it typically takes only hours not days. 

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

I did the implementation of the solution.

The price of Bamboo is reasonable.

There is maintenance needed for keeping track of the nodes and making sure the agents are live. However, the solution does not require a lot of effort for maintenance of the solution. We use two people for the maintenance.

I would recommend this solution to others.

I rate Bamboo a nine out of ten.

The solution helps us automate tasks and save development and testing time. We can migrate multiple scripts and execute them. 

We use Bamboo to automate all our test builds and deployments. It integrates with tools like the ReportPortal to help us check and evaluate processes. When we initiate commands, it automatically checks for scaling issues or failures related to new code. Based on these evaluations, it provides reports in the ReportPortal, helping us decide whether to implement changes.

The tool is user-friendly and easy to integrate. 

Integrating workflows with other platforms can be challenging. The capabilities of these platforms sometimes fall short compared to others. Initially, it was difficult for us because the plugins were very limited.

I have been working with the product for a couple of months. 

I rate the solution's stability a nine out of ten. 

I rate Bamboo's scalability an eight out of ten. My company has around 2000 users. 

Bamboo's support is very helpful. We have a dedicated Slack channel with their support team. Whenever we ask for help, they respond within minutes.

Bamboo works very seamlessly compared to others. For instance, with GitHub Actions, automation might fail while building the image or caching some libraries. However, Bamboo doesn't have these issues.

The tool's deployment is good and takes around three to four hours to complete. 

I rate the solution's pricing a three out of five. 

I rate the overall solution an eight out of ten. 

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.

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.

We use Bamboo to deploy our apps to local test servers and then to production.

The most useful feature of Bamboo is its integration with other solutions such as Jira and BitBucket, also offered by Atlassian. It is easier to use tools all provided by one vendor. 

We are considering moving to a cloud solution and to use Bitbucket pipeline because of the features it offers. From a hosting perspective, it's easier to make use of solutions that are hosted in the cloud rather than to maintain the tool on-premise. This is not feasible with Bamboo. 

A feature I would like to see added is the integration with quality assurance reports when you run automated tests such as a Selenium test. It would be great to have the results visualised to understand the quality of a build. It is possible to do this manually but it requires a lot of configuration. 

Scalability depends on the use case. If it is really a big customer with a lot of tests, it might not be a scalable option for them.

One of our enterprise customers were not satisfied with the scalability of the solution. This customer wanted to develop a financial system and needed to run an enormous amount of tests automatically which resulted in some problems. 

In some countries, the local or technical support for some solutions from Atlassian is not present. You need to go to the community to write your question or write a ticket to Atlassian to access their support team.

Their response is not always very useful. Some of the questions they have answered quickly and correctly; other questions have taken longer. 

Positive

The initial setup was straightforward but we are an IT company so did this easily with the resources we have. 

The server products for small teams used to offer excellent pricing. However, Atlassian has since changed the offering and the pricing is more expensive. I do still think the solution offers good value for money.

I would advise those investigating this solution to start small with a step-by-step approach and adapt as their experience grows. I would suggest that you start with the build, and once you master the build, focus on deployment. It is important to consider whether an on-premise or cloud solution is best suited before getting started. 

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.