When comparing CloudBees vs Bamboo, the Slant community recommends CloudBees for most people. In the question“What are the best hosted continuous integration services?” CloudBees is ranked 8th while Bamboo is ranked 12th. The most important reason people chose CloudBees is:
Quick access to experts who are responsive, helpful, and friendly.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Great enterprise level support
Quick access to experts who are responsive, helpful, and friendly.
Pro Private and internal SVN and Git repositories
Support for both SVN and Git private repositories.
Pro Highly customisable
Jenkins is by far the most customizable solution on the market. And CloudBees is built on Jenkins. There are over 400 plugins to support building and testing virtually any project.
Pro Free for open source projects
CloudBees offers a solution for owners and developers of free and open source projects to be hosted and built by their service.
Pro Fine-grained control over each environment the project needs to be deployed to
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.
Pro End-to-end visibility when linked to JIRA, Stash and HipChat
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.
Pro Integration with Docker
Bamboo allows using Docker containers to create build agents. Using Docker agents lets you run multiple remote agents on the same host without conflicting requirements. It makes it easier to duplicate and distribute changes to build agents, and to use scripts for creating and maintaining agents.
How can you define and build your own image and push it to a registry to share? This is when Bamboo’s Docker tasks come into play. Docker tasks make it possible to build an image, run a container, and push a Docker image to a registry from within your build or deployment project.
Pro Out-of-the-box support for Git branching workflows
Bamboo allows you to automatically detect and build new branches, merge branches together when tests pass and continuously deploy code to staging and production servers based on branch name.
Pro Test automation
Out-of-the-box features that let developers perform parallel testing on elastic agents and quarantine flakey tests.
Pro Easy enterprise-grade administration
Avoid plugin hell by having most important capabilities as out-of-the-box features, not plugins. Bamboo is not just built for teams, but teams-of-teams. It has the administrative features you need to manage and maintain CI at scale. Enterprise model for access control, management, and support.
Pro Bundled AWS CodeDeploy task
Deploying applications with AWS CodeDeploy was always possible by using Bamboo script tasks, and it's now an easier process with a bundled add-on and its accompanying CodeDeploy task.
Pro Integration with Amazon S3
Bamboo can also be integrated with Amazon S3 for unlimited storage.
Cons
Con Java-only solution (without plugins)
Jenkins supports only software built with Java (unless you use plugins)
Con Very limited basic license.
Although they have $10 license it is very limited even for modest shops. Even next step of commercial license is very expensive for what you get.
Con Bamboo Cloud is going away in Jan. 2017
Migration to Bamboo Server is non-trivial and may not be worth the effort.
Con 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.