Overview
What is Bamboo?
Australian company Atlassian offers Bamboo, a continuous integration server.
Feature-rich, easy to use CICD tool with a few rough edges for enterprises
Excellent Collaboration solution for IT Teams
Bamboo a great software for streamlining goal setting, employee reviews and hiring.
Good CI/CD solution for your engineering tool chain
Bamboo Review
Bamboo useful addition to Atlassian stack
A lightweight tool for CI/CD
Bamboo for Enterprise solutions
Bamboo for Continuous Deployment and Continuous Integration
Bamboo - Continuous Integration
Bamboo? Woohoo!
Review for Bamboo
A consultant view on Bamboo
Bamboo Review
Easy to Set Up, Great CI
Pricing
What is Bamboo?
Australian company Atlassian offers Bamboo, a continuous integration server.
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
5 people also want pricing
Alternatives Pricing
What is CircleCI?
CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so…
What is Heroku Platform?
The Heroku Platform, now from Salesforce, is a platform-as-a-service based on a managed container system, with integrated data services and ecosystem for deploying modern apps. It takes an app-centric approach for software delivery, integrated with developer tools and workflows. It’s three main…
Product Demos
sumi-e bamboo demo
Zumba Demo - Bamboo(Hips Don't lie) - Shakira
Acrylmalen: Malen lernen, Übungen zum Bambus/ Acrylic painting Tutorial Demo, bamboo painting
TARTE Airbrush Bamboo Foundation Brush Demo
Wood & bamboo fire pistons, demo by maker
Wacom Bamboo Spark Demo & Review inc Unboxing #BambooSpark
Product Details
- About
- Integrations
- Tech Details
- FAQs
What is Bamboo?
Bamboo Video
Bamboo Integrations
Bamboo Technical Details
Operating Systems | Unspecified |
---|---|
Mobile Application | No |
Frequently Asked Questions
Comparisons
Compare with
Reviews and Ratings
(92)Community Insights
- Business Problems Solved
- Pros
- Cons
- Recommendations
Bamboo is a versatile tool that has been widely adopted by various organizations for continuous integration and deployment processes. CDK Global, a leading tech company, relies on Bamboo as their primary tool for building products in a reproducible way and deploying them to different environments. According to CDK, Bamboo solves the problem of relying on individual developers' computers by ensuring a consistent build process. The seamless integration between Bamboo and other Atlassian products allows users to easily manage plans with a single button click.
Another use case for Bamboo is in the BI SQL development team, where it is used to implement a controlled and continuously integrated development environment. This enables the team to build the production server directly from source control. Additionally, Bamboo has been successfully used by different departments within organizations to automate the build process, achieve continuous integration, and streamline branch merging. Its integration with Bitbucket makes it an attractive choice for both internal and customer-facing applications.
Moreover, Bamboo finds value in its ability to automate testing scripts and monitor highly transactional web applications around the clock. Users have reported that Bamboo is an enterprise-friendly tool that supports fast and continuous partitioning of build and deployment tasks. It offers simple build configuration, multiple notification methods, and integrates well with other Atlassian products like JIRA. Bamboo's popularity also stems from its support for builds in any programming language using various build tools like Ant, Maven, and Make.
In summary, Bamboo proves to be a valuable asset for teams seeking an effective continuous integration and deployment solution. Its features have been commended by users who have found success in automating their build processes, achieving seamless integration with other tools, and maintaining control and visibility throughout their development workflows.
High Level of Granularity: Many users have praised Bamboo for its high level of granularity, allowing them to effectively manage complex software development processes. This feature enables users to organize multiple projects, build plans, jobs, and tasks with ease.
Versatility for Different Programming Languages and Operating Systems: Several reviewers have highlighted the versatility of Bamboo in managing build plans for various programming languages such as Java, Node, and .NET. Additionally, Bamboo's support for different operating systems like Mac, Windows, and Linux has been appreciated by users. This flexibility allows users to adapt Bamboo to their specific development needs.
Integration with Other Atlassian Products: The integration of Bamboo with other Atlassian products like Bitbucket, Stash, and JIRA has received positive feedback from many customers. Reviewers have mentioned that this integration provides valuable traceability throughout the entire development lifecycle. It allows users to track work seamlessly and streamlines the development process.
Inaccurate build duration estimation: Some users have reported that Bamboo's estimation of build duration is often inaccurate, with the progress bar completing before the build is actually finished.
Complexity for non-backend developers: Several reviewers have mentioned that non-backend developers face a significant barrier to entry when using Bamboo due to its complexity, which makes it challenging for them to customize functionality or debug build issues.
Lack of cloud solution and limited scalability: A number of users have expressed frustration over the fact that Bamboo does not offer a cloud solution and lacks the scalability of other tools like Jenkins. They also feel that it is not as user-friendly as CircleCI and has limitations in terms of deployment plans and compatibility with newer cloud deployment patterns.
Users commonly recommend the following when it comes to Bamboo, based on their experiences:
Evaluate and Compare: Users frequently advise evaluating Bamboo against other similar products in order to find the best fit for their needs. They suggest thoroughly testing Bamboo before making a purchase to ensure it meets specific requirements. Furthermore, users recommend comparing Bamboo with Jenkins, another popular CI/CD tool, to determine if one solution might suffice without the need for integration with additional Atlassian products.
Integrate and Automate: A common recommendation is to integrate Bamboo with other Atlassian tools, such as Bitbucket and GitHub, for seamless automation and issue tracking. Users highlight Bamboo's nice set of features for Maven and npm builds. Several users suggest combining Bamboo with Jira or Stash for an enhanced experience. They also mention that integrating with AWS requires hiring an AWS certified Sysadmin for proper setup.
Test and Train: Users stress the importance of fully testing Bamboo before committing to a paid tier, suggesting utilizing the trial period to see if it aligns with their company's requirements. They also recommend ensuring proper training for the entire team to maximize Bamboo's capabilities. Understanding the build process and translating instructions to Bamboo's plugins is emphasized as an essential step in successful implementation.
Overall, users find Bamboo highly recommendable for Continuous Integration-Continuous Deployment (CI/CD), especially when integrated with other Atlassian products. They appreciate its ease of use, clean UI, built-in features, and enterprise-ready capabilities. However, they emphasize the need to compare, evaluate, test thoroughly, integrate wisely, and invest in knowledge and expertise for a successful implementation of Bamboo.
Attribute Ratings
Reviews
(1-21 of 21)- Straightforward/easy to use web interface
- Wide variety of tasks and plugins available
- Built-in artifact repository
- Not aware of newer cloud deployment patterns such as blue/green
- Pipeline-as-code (Java Specs, yml) can be frustrating to use
- Difficult to share variables/secrets between build projects and deployment projects
- Difficult to adhere to segregation of duties requirements using access controls
The scenarios that it doesn't deal with particularly well are edge cases such as segregation-of-duties, secrets management, or scaling to support a very large number of projects/pipelines - things that matter in large enterprises with many regulatory requirements, though I suspect those are difficult to fulfill using any similar tool.
Excellent Collaboration solution for IT Teams
- Tracking
- Integration with other Atlassian products
- Automation
- Reliability
- Support needs to be improve
- Dashboard is a little limited
- Easy to use interface when submitting, editing, and reviewing goals.
- It offers a streamlines a communication process between individuals and reminders.
- None, I like the software!
Good CI/CD solution for your engineering tool chain
If you are also using Bitbucket and Jira, then you can start to appreciate the full potential of Bamboo as it integrates with both systems very well. When fully integrated, you will be able to have insight into the exact code change that triggers the build and test failure. This is very helpful to track down issues and if you need to decide on if a particular feature the team is working on (referenced by the code change) needs to be pushed back for a week.
Bamboo Review
- Sharing of source code.
- Compliant source code.
- Administration could be simplified.
- Rights more granular.
Bamboo useful addition to Atlassian stack
- Pipelines as code
- Build pipelines
- Deployment pipelines
- Deployment plans are a little rudimentary
- The interface can be disorganized at times, especially the admin interface
A lightweight tool for CI/CD
- It is fairly light weight and can be easily customized
- Very easy to set up
- Integrates well with other Atlassian products
- Additional cost if you want agents on other cloud services
- Requires a dedicated machine and can require a decent amount of processing power depending on the agent you are running
Bamboo for Enterprise solutions
- Easily integrated with Bitbucket
- Easily integrated with JIRA
- Fairly simple interface
- Interface felt as if it was bolted on and not contiguous
- Not great at integrating with Microsoft Tools
- Not great for deployment to IIS
Bamboo for Continuous Deployment and Continuous Integration
- Continuous Deployment - you can use Bamboo to automatically build and deploy whenever there are changes in the source code.
- Continuous Integration - by integrating the automated tests and the integration tests before deploying you make sure you know immediately if the latest code fits into the whole scheme of apps.
- Integration with Jira and Bitbucket.
- Flexibility with the program language used for builds: Maven, Ant, PowerShell, any command line tools.
- When you have more complex applications using different technologies, it can be a pain to initially set up all scripts for deploy and test.
- Flexibility to use many build technologies at a lower level comes also with a problem that sometimes it is difficult to see from the interface what exactly is wrong with the build if the scripts are not handling errors very well. This can take lot of time to debug.
- May take some time for the team to learn the product and use it at its full potential.
Bamboo - Continuous Integration
- Seemless integration with Atlassian products
- Easy to set up and use
- Helpful support from Atlassian
- Plugins are expensive
- Not open-source
- Community of users is much smaller than competitors such as Jenkins
Bamboo? Woohoo!
- Continuous Integration - Bamboo kicks off builds with each check in to our source control system, enabling faster consumption of changes, and quicker turnaround times when we encounter a problem.
- Extensibility - Bamboo is capable of triggering multiple additional processes on completion of a build, including integration tests, deployment tests, and the like. This extensibility took us from a scheduled based system to a trigger based system with little time waste.
- Suite Integration - Bamboo's easy integration with the rest of the Atlassian suite makes for huge efficiency gains. Being able to see which check in triggered the build, as well as seeing what JIRA issues went into that check-in makes for complete traceability.
- Cost - Obviously, purchasing licensing for the Atlassian toolset is more expensive than a roll your own approach with other open source packages, but the tight integration amongst the tools makes up for that cost.
- Plugins - Bamboo does not have quite the rich ecosystem of plugins that other open source tools, like Jenkins does.
- Agents - We preferred the build agent model offered by Jenkins because of its far cheaper costs. Because of the costs of Atlassian agents, we are limited in the number of agents we deploy.
Review for Bamboo
- Integrated with Make and Ant
- Integrated with other Atlatissan products
- Not free after 10 jobs. They will charge money when you have more than 10 jobs.
A consultant view on Bamboo
- It does perfectly well what is it supposed to do, build code on a centralized server.
- You can run automated tests on any new code you build.
- It can look hard to set up at first, because of the needed integrations with other tools.
- Not interesting to use without other Atlassian tools.
- Maybe more options for tests, some could be automated.
It is not suited for small teams that are not using other Atlassian tools, which should look for simpler software.
Bamboo Review
- Returns extensive logging from the called application.
- Easy to use.
- Many task options
- Not much support from the java/jdk side. Had some memory issues where the jvm was pegging the application server. Once identified and resolved, haven't had a single issue.
Easy to Set Up, Great CI
- Easy installation
- Integration with Atlasian products
- Simple build configuration
- More cost efective plugins
- Slows as user base and builds increases
- Granular email notification
- We had multiple teams working on the same code base so we wanted a good CI and well-defined plans and triggers to make sure bad code is not committed,
- Easy to use UI helped us to get new resources easily onboard
- Bamboo helped us to execute the build on specific triggers making sure they are compliant
Bam!Boo!
Bamboo is used across the organization for all R&D of new products. CDK is working to transition all products to use Bamboo, but it has a lot of them. Bamboo solves the problem of needing to build a product in a reproducible way that is not dependant on anything that exists on an individual developer's computer. It allows us to deploy a deterministically generated image from a central location. I think that Bamboo is a good product, but CDK could make better use of it if they could start all over, but they are sort of stuck with the current implementation they have because it is hard to change quickly.
- Levels of granularity. Organization has many projects that have many build plans that have many jobs that have many tasks, etc. And branch builds allow source control branches to be built separately.
- Versatility. I can use bamboo to manage my Java, node, or .NET build plans. I can use it to spin up Windows or Linux build agents, or install it on a Mac to build there as well.
- Unclear what different levels of granularity should be used for. How is a Job and a Task and a Build and a Project different? It requires a consultant to help not make a mess of this. It takes a while to search all the Projects in CDK, there are way way too many.
- Not particularly useful compared to free open source solutions, unless you buy into other Atlassian products. I.e. most of the value is in the integration
- Bamboo is not great at estimating how long a build will take. The progress bar for a build completes long before it it is actually done.
Bamboo - when hosting your own CI solution is your preference
The caveat to all of this, is we are currently moving off of Bamboo to TeamCity by Jetbrains, as we were making use of the Bamboo cloud services, and were/are not interested in self-hosting.
- Integrations with the rest of the Atlassian suite - specifically bitbucket.
- Fast, automated build workflow...very hands-off for us.
- The soon-to-be lack of a cloud solution has lost us as a customer. :(
Bamboo is for enterprise, but not for everyone.
- Rapidly setting up build plans
- Being a central hub into all activity your company is a part of
- Offering an intuitive UI
- Allowing power-users to set up powerful CI/CD pipelines
- Unit testing FTW
- Extremely hard barrier to entry for non-backend developers
- Blackbox makes it hard to customize functionality
- The inability to add features without breaking core functionality
- No cloud solution
- Tasks cannot be put in if/else statements
- No clear right way to form build plans
Bamboo really falls apart when working in small cross functional teams. Due to the complexity involved in setting up build agents, this product can only work in certain use cases, and with people of certain (high) skill levels. Also, if you want to add any sort of logic or AI to your build and deployment, Bamboo simply can't do that. Not being able to add logic and machine learning to my deployments is a dealbreaker for me, as I count on multiple business use cases to deploy code.
- Bamboo builds our release branches and automatically merges them with our master branch if a build succeeds.
- Bamboo allows our developers to see if a build succeeds in their feature or bug fix branches before they merge it into a release branch.
- Bamboo builds our software immediately after a checkin and provides immediate feedback as to whether the build succeeds or fails.
- Bamboo configuration is done through the web interface and as a result cannot be versioned. It would be nice if the build configuration could be versioned.
- Sometimes it isn't obvious how to pass artifacts between build plans. This can be confusing when trying to put together a build plan that depends on a different build plan.
- It would be useful to be able to execute some jobs only in certain branches instead of for all branches. For instance, when using plan branches, we'd prefer to only push release branches to artifactory and not plan branches.
Great flexibility within Atlasssian product family
- Build automation - Bamboo gives almost too many ways to automate things via its partitioning of jobs and tasks to give the script builder and dev-ops flexibility.
- Continuous integration - Because of Atlasssian's well-known integrative software with other interfacing CD and CI tools, automation is as easy as a simple script to hook up the connections and automate things with ease.
- Continuous deployment - Triggers for sending complete builds to production or other test environments are quite configurable.
- Free open-source require application to use - Bamboo does offer a free option for open source projects though it requires the user to apply for it in order to use it past the free trial.
- Too many options - Supposing you are an end-user, the many different options are nauseating and can cause many headaches trying to debug.
- Pricey for small user base - You can try it for 30 days for $10 with no remote agents but one remote agent costs $800.
When connecting Bamboo with Stash and JIRA, details like JIRA issues, commits, reviews and approvals follow each release from development to production. If HipChat is part of the integration, team members get notified right away in addition to email notifications.
Deployment Projects -
Bamboo is the only build server to offer first-class support for the "delivery" aspect of continuous delivery. Deployment projects automate the tedium right out of releasing into each environment, while letting you control the flow with per-environment permissions.
Bamboo has a clean friendly UI
- Provides a user-friendly UI compared to Jenkins
- Provides a dashboard where users can download artifacts
- Provides good status indicators and email notifications of build status/progress
- Doesn't have Jenkins' scaling abilities with their Swarm agents.
- Isn't as user-friendly as CircleCI.
- Is too centrally managed (probably more an indicator of our usage than the product though)...most companies let the developers have admin access to the build server.
- Doesn't have as many plugins as Jenkins to do various things like upload to servers, etc.