It works. Out of the box. Well, you have to migrate to a proper database (the default installation uses an embedded H2/HSQL), but even that is not a hussle. There's a log analyzer that reports on the health of the server. Automatic backups on your schedule. The distinction between build and deployment projects and artifact sharing. Support for multiple deployment environments and tracking the deployed versions/builds for each environment. Agent infrastructure, so you can have build agents on different platforms. Great maven integration. Plenty of add-ons for integrating with peripheral tools such as SonarQube, Artifactory, npm etc.
Not much. Not zero, zilch, zip, nada, nothing, nil or null, but so little it does not directly come to mind.
1. Nice set of features for Maven and npm builds.
2. Plenty of add-ons on the Atlassian market-place, most free.
3. Administration is straight-forward.
4. Build and failed build RSS feeds can be consumed by monitoring software.
5. Buy agent licenses if you need to build for multiple platforms (e.g., if your main platform is Linux and Java and you have installed Bamboo on Linux, to build .NET projects you'll need an agent on a Windows server, to build IOS apps you'll need an agent on a Mac)
We have Java and Node.JS code to Kubernetes deployment pipelines in place for multiple projects and use Bamboo for continuous integration and delivery. The pipelines involve package publishing on Maven or npm and SonarQube analysis. We use Atlassian BitBucket (git repo, formerly Atlassian Stash) for source code control and they fit like a hand and a glove.
The mobile team also runs their builds on Bamboo, we have a dedicated Mac Bamboo agent for iPhone builds.