Build, test, and deploy your applications with Atlassian Bamboo
January 16, 2020
Build, test, and deploy your applications with Atlassian Bamboo

Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Bamboo
We use Atlassian Bamboo as our continuous integration/continuous delivery (CI/CD) solution. All of our products in the organization are built using Bamboo as the main build environment. It is an integral part of our build pipeline, as we use it to:
Pros
- Cross-reference builds test cases and results with other systems for better traceability.
- Support wide variety of build tools and deployment environments.
Cons
- More support for common build tools out of the box (non-Java based tools).
- Add more permission levels and controls for build plans.
- Automated CI/CD pipeline for streamlined delivery.
- Faster feedbacks on code changes for engineers.
In terms of features and capabilities, Bamboo and Jenkins have a very similar offering for what we need. The feature that made Bamboo stand out more if its cross-reference capability with Jira and Bitbucket. We really loved the ability to see which code commit triggered a build, as well as the tasks that the commits are for. And the ability to see the same information "in reverse", i.e. which commits and issues belong to a build is also very useful. We did run into a few instances where Bamboo falls short in terms of features (non-critical) compared to Jenkins, but thanks to its extensibility and ecosystem, we were able to find 3rd party add-ons that helped to bridge the gaps.
Do you think Atlassian Bamboo delivers good value for the price?
Yes
Are you happy with Atlassian Bamboo's feature set?
Yes
Did Atlassian Bamboo live up to sales and marketing promises?
Yes
Did implementation of Atlassian Bamboo go as expected?
Yes
Would you buy Atlassian Bamboo again?
Yes
Comments
Please log in to join the conversation