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

Build, test, and deploy your applications with Atlassian Bamboo

Patrick Li | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source

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:
  • Automatically build our codebase whenever changes occur.
  • Run test cases and report any issues found.
  • Deploy built artifacts to the target the environment.
  • Cross-reference builds and results with other systems such as Jira issues and Bitbucket (Git) commits.
  • Cross-reference builds test cases and results with other systems for better traceability.
  • Support wide variety of build tools and deployment environments.
  • 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.
Atlassian support is also great for all its offerings including Bamboo. However, we feel that Bamboo does not get as much love as some of their more popular offerings such as Jira and Confluence, and it sometimes takes a bit longer for issues and feature requests to get addressed in comparison.

Do you think Bamboo delivers good value for the price?


Are you happy with Bamboo's feature set?


Did Bamboo live up to sales and marketing promises?


Did implementation of Bamboo go as expected?


Would you buy Bamboo again?


Atlassian Bamboo is a good CI/CD solution, especially if you are already using Atlassian JIRA for issue tracking and Bitbucket (Git) for source code management. Together, these three systems can cross-reference data from each other to provide you with a holistic view of what is happening with your code commits and builds. For example, if a build fails, you will be able to tell which commit caused the failure and the issue/task that the commit is meant for, all from within the same user interface. Bamboo works particularly well if you are using Maven as the build tool as it comes with good support for it out of the box.

If you are using different tools, such as GitHub instead of Bitbucket, you can still get the synergy above, but not quite to the same level, in which case, you might want to consider other alternatives, e.g. using the GitHub stack.