Bamboo is made by Atlassian, the company that also made and maintains tools such as JIRA, Stash and BitBucket, so it's a given that they would integrate quite nicely. For example, when connecting Bamboo with Stash and JIRA, details like JIRA issues, commits, reviews and approvals follow each...
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.
Since Jenkins and Hudson share much of the same code base, they also share many of the same features. Hudson is also very easy to install, just a single .war file which is run inside the root of the directory where Hudson will be installed.
Jenkins is a fork from Hudson and as such it inherits most of it's source code. But Jenkins has far more commits and is a lot more active on the development side than Hudson. A lot of plugin developers have also chosen to support Jenkins and develop their product for Jenkins only.
Even though Jenkins comes pretty functional and useful out of the box, there's a large plugin ecosystem from which you can choose plugins to integrate into your Jenkins build if you want to extend any of its features.
Builds only run on Jenkins agents, not locally, so it is hard to find and fix problems in build jobs. Worse, the UI compounds the problem. Trying to find the build output log for a failed build in Jenkins can be up to 3 clicks from the home page.
The flip side of "highly customizable" is that things most people want to do still require plugins not installed out-of-the-box. Worse, some common capabilities will require multiple plugins to get working right. The overhead of adding so many plugins amplifies many of the other cons. Al...