Australian company Atlassian offers Bamboo, a continuous integration server.
N/A
Pricing
Bamboo
Editions & Modules
No answers on this topic
Offerings
Pricing Offerings
Bamboo
Free Trial
No
Free/Freemium Version
No
Premium Consulting/Integration Services
No
Entry-level Setup Fee
No setup fee
Additional Details
—
More Pricing Information
Community Pulse
Bamboo
Considered Both Products
Bamboo
Verified User
Engineer
Chose Bamboo
We selected Bamboo because its capabilities to integrate with other Atlassian products specially Jira Software, Bitbucket and in some useful scenarios with Confluence. Also, we found these pros important for us: great user interface, easily agent deployment, Docker …
Bamboo's ability to integrate with Bitbucket and Jira (the other two key systems we use) pretty much sealed the deal on our decision to choose Bamboo over other alternatives. Being able to map every build result back to the relevant code changes and Jira issues are just too …
Jenkins is the only other we had briefly considered for continuous deployment type of products, but being open source could not get the same level of reliability and support offered from Bamboo's product maturity.
We looked at Bitbucket and some other providers but they did not have the full requirements that we needed from a customization perspective. We wanted customization while keeping a lot of the configurability intact.
In the beginning we had selected Bamboo and were down the path of going all in for all of our projects. However after about a year we decided that Azure DevOps was better suited for our business needs. We are now in the process of migrating everything off of the Bamboo …
We used Jenkins before for our projects. While Jenkins has an extensive plugins list that makes it more flexible to integrate it with other tools, we switched to Bamboo for nicer User Interface but mostly for the seamless integration with Jira and Bitbucket. Also Bamboo has more …
Bamboo is great tool when compared to the open-source alternative Jenkins, with mainly the same functionality in both it really shines with its integration of the Atlassian product line. Jenkins works really well with a huge community of users and plenty of plugins that are …
We chose Bamboo over Jenkins for 2 reasons - one, for its tight integration amongst all the products in the tool suite. We find explicit value in the traceability from JIRA issues all the way down to the Bamboo build that was triggered by the check in of those issues. The …
Jenkins works great, but Bamboo is just fantastic when integrated with other Atlassian tools. Since we were using JIRA and Bitbucket, we went for Bamboo.
I use bamboo because it is mandated as the CI/CD solution to use across the organization that I work for. If I were working on my own project, I would almost certainly use a free solution like Travis CI or just spin up my own build servers using Docker, AWS, or something like …
Bamboo won solely based on the fact we were "all-in" with Atlassian. TeamCity is now in the process of taking over as we transition off of Bamboo, and I think TeamCity stacks up nice against Bamboo thus far (too soon to tell).
Bamboo integrates directly with our bug system (JIRA) and source control system (Bitbucket). It allows us to get what we need to done without worrying about how it works with our other systems.
Bamboo is hands-down the best of these options if you rely on other products of Atlassian origin. Bamboo is not just built for teams, but teams-of-teams and teams of many workers. It has the administrative features you need to manage and maintain CI at scale. Enterprise model …