Bamboo

Straightforward/easy to use web interface

Excellent integration with Atlassian Bitbucket and Jira

Wide variety of tasks and plugins available

Built-in artifact repository

Not aware of newer cloud deployment patterns such as blue/green

Pipeline-as-code (Java Specs, yml) can be frustrating to use

Difficult to share variables/secrets between build projects and deployment projects

Difficult to adhere to segregation of duties requirements using access controls

Tracking

Integration with other Atlassian products

Automation

Reliability

Support needs to be improve

Dashboard is a little limited

Easy to use interface when submitting, editing, and reviewing goals.

It offers a streamlines a communication process between individuals and reminders.

None, I like the software!

Integration with Bitbucket and Jira

Excellent maven support

Better support for non-Java based projects

When your project does not follow the "standard" maven set up or becomes complex, it can be complicated to make it work with Bamboo.

Sharing of source code.

Compliant source code.

Administration could be simplified.

Rights more granular.

Pipelines as code

Build pipelines

Deployment pipelines

Deployment plans are a little rudimentary

The interface can be disorganized at times, especially the admin interface

It is fairly light weight and can be easily customized

Very easy to set up

Integrates well with other Atlassian products

Additional cost if you want agents on other cloud services

Requires a dedicated machine and can require a decent amount of processing power depending on the agent you are running

Easily integrated with Bitbucket

Easily integrated with JIRA

Fairly simple interface

Interface felt as if it was bolted on and not contiguous

Not great at integrating with Microsoft Tools

Not great for deployment to IIS

Continuous Deployment - you can use Bamboo to automatically build and deploy whenever there are changes in the source code.

Continuous Integration - by integrating the automated tests and the integration tests before deploying you make sure you know immediately if the latest code fits into the whole scheme of apps.

Integration with Jira and Bitbucket.

Flexibility with the program language used for builds: Maven, Ant, PowerShell, any command line tools.

When you have more complex applications using different technologies, it can be a pain to initially set up all scripts for deploy and test.

Flexibility to use many build technologies at a lower level comes also with a problem that sometimes it is difficult to see from the interface what exactly is wrong with the build if the scripts are not handling errors very well. This can take lot of time to debug.

May take some time for the team to learn the product and use it at its full potential.

Seemless integration with Atlassian products

Easy to set up and use

Helpful support from Atlassian

Plugins are expensive

Not open-source

Community of users is much smaller than competitors such as Jenkins

Continuous Integration - Bamboo kicks off builds with each check in to our source control system, enabling faster consumption of changes, and quicker turnaround times when we encounter a problem.

Extensibility - Bamboo is capable of triggering multiple additional processes on completion of a build, including integration tests, deployment tests, and the like. This extensibility took us from a scheduled based system to a trigger based system with little time waste.

Suite Integration - Bamboo's easy integration with the rest of the Atlassian suite makes for huge efficiency gains. Being able to see which check in triggered the build, as well as seeing what JIRA issues went into that check-in makes for complete traceability.

Cost - Obviously, purchasing licensing for the Atlassian toolset is more expensive than a roll your own approach with other open source packages, but the tight integration amongst the tools makes up for that cost.

Plugins - Bamboo does not have quite the rich ecosystem of plugins that other open source tools, like Jenkins does.

Agents - We preferred the build agent model offered by Jenkins because of its far cheaper costs. Because of the costs of Atlassian agents, we are limited in the number of agents we deploy.

Integrated with Make and Ant

Integrated with other Atlatissan products

Not free after 10 jobs. They will charge money when you have more than 10 jobs.

It does perfectly well what is it supposed to do, build code on a centralized server.

The super power of Bamboo is being part of the Atlassian suite. With the right integration, pushing code to Bitbucket would trigger a build by Bamboo, send the results in Hipchat and update tickets in JIRA. It is pure magic.

You can run automated tests on any new code you build.

It can look hard to set up at first, because of the needed integrations with other tools.

Not interesting to use without other Atlassian tools.

Maybe more options for tests, some could be automated.

Returns extensive logging from the called application.

Easy to use.

Many task options

Not much support from the java/jdk side. Had some memory issues where the jvm was pegging the application server. Once identified and resolved, haven't had a single issue.

Easy installation

Integration with Atlasian products

Simple build configuration

More cost efective plugins

Slows as user base and builds increases

Granular email notification

Build Automation

Continuous Integration

Configuration Management

Continuous Deployment

They could improve their pricing model for smaller teams

They can focus on mobile applications

The build plans seem to fail quite frequently. This occurs for no apparent reason. If it fails once, we will attempt to deploy again. Usually, after 2-3 times it will work.

Levels of granularity. Organization has many projects that have many build plans that have many jobs that have many tasks, etc. And branch builds allow source control branches to be built separately.

Versatility. I can use bamboo to manage my Java, node, or .NET build plans. I can use it to spin up Windows or Linux build agents, or install it on a Mac to build there as well.

Bamboo integrates with other Atlassian products like Bitbucket, Stash, JIRA, etc. If a company commits to the entire Atlassian stack then work can be tracked through the whole development lifecycle which is really useful.

Unclear what different levels of granularity should be used for. How is a Job and a Task and a Build and a Project different? It requires a consultant to help not make a mess of this. It takes a while to search all the Projects in CDK, there are way way too many.

Not particularly useful compared to free open source solutions, unless you buy into other Atlassian products. I.e. most of the value is in the integration

Bamboo is not great at estimating how long a build will take. The progress bar for a build completes long before it it is actually done.

Integrations with the rest of the Atlassian suite - specifically bitbucket.

Fast, automated build workflow...very hands-off for us.

The soon-to-be lack of a cloud solution has lost us as a customer. :(

Rapidly setting up build plans

Being a central hub into all activity your company is a part of

Offering an intuitive UI

Allowing power-users to set up powerful CI/CD pipelines

Unit testing FTW

Extremely hard barrier to entry for non-backend developers

Blackbox makes it hard to customize functionality

The inability to add features without breaking core functionality

No cloud solution

Tasks cannot be put in if/else statements

No clear right way to form build plans

Bamboo builds our release branches and automatically merges them with our master branch if a build succeeds.

Bamboo allows our developers to see if a build succeeds in their feature or bug fix branches before they merge it into a release branch.

Bamboo builds our software immediately after a checkin and provides immediate feedback as to whether the build succeeds or fails.

Bamboo configuration is done through the web interface and as a result cannot be versioned. It would be nice if the build configuration could be versioned.

Sometimes it isn't obvious how to pass artifacts between build plans. This can be confusing when trying to put together a build plan that depends on a different build plan.

It would be useful to be able to execute some jobs only in certain branches instead of for all branches. For instance, when using plan branches, we'd prefer to only push release branches to artifactory and not plan branches.

Build automation - Bamboo gives almost too many ways to automate things via its partitioning of jobs and tasks to give the script builder and dev-ops flexibility.

Continuous integration - Because of Atlasssian's well-known integrative software with other interfacing CD and CI tools, automation is as easy as a simple script to hook up the connections and automate things with ease.

Continuous deployment - Triggers for sending complete builds to production or other test environments are quite configurable.

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.

Too many options - Supposing you are an end-user, the many different options are nauseating and can cause many headaches trying to debug.

Pricey for small user base - You can try it for 30 days for $10 with no remote agents but one remote agent costs $800.

Provides a user-friendly UI compared to Jenkins

Provides a dashboard where users can download artifacts

Provides good status indicators and email notifications of build status/progress

Doesn't have Jenkins' scaling abilities with their Swarm agents.

Isn't as user-friendly as CircleCI.

Is too centrally managed (probably more an indicator of our usage than the product though)...most companies let the developers have admin access to the build server.

Doesn't have as many plugins as Jenkins to do various things like upload to servers, etc.