Bamboo Reviews & Product Details

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.

Integration with Atlassian stack, you can:

* view builds and releases that are related to specific issues

* run builds by releasing out of JIRA directly

* display build/deploy reports in JIRA and Confluence

* view code changes and reviews that are related to your builds

It also has excellent support for Maven out of box, making it very easy to:

* configure build plans for projects that use Maven

* release codes that uses the Maven release plugin

There are also 3rd party add-ons you can use (for on-prem) for things it does not support out of box, or if you want, create your own add-ons.

Outside of Maven, its support for other build tools is not as good. Especially when it comes to making releases. Because it uses the maven-release plugin, there are some "magic" it uses, which is not available in other tools, and you will end up writing command line scripts to work around it to have the same result.

If you are using Atlassian products and Maven, Bamboo is the perfect CI/CD solution for you.

End to end build automation and deploying to various environments with different configurations. Allows for a streamlined build, release, deploy cycle.

Atlassian Bamboo is great and very easy in configuring the integration and deployment plans.

Atlassian provides all the features documented over the cloud.

It is finely integrated with other atlassian products like HipChat, Confluence, Bitbucket, etc.

memory management seems poorly implemented, since it piles up the heap space frequently.

Sometimes it hangs and goes out of memory as well.

Consider memory issue while choosing bamboo.

It is also not much secure.

We are using Bamboo for automating the Integration and deployment plans.

The basic build automation process, though not flashy, is probably the biggest win for us. One of the specific features we rely on is the ability for our Bamboo build process to parse Junit report outputs. We have written a number of validation tests that are executed during the validation portion of our builds. Note that that may not be novel from a software perspective, but we also have a number of configuration repositories against which we also run these validation steps to identify errors in the configuration and/or changes that should not have been made.

We work with a separate team responsible for the actual configuration and behind-the-scenes work, so from where we sit there are a few things that just "magically" work or fail horribly. Something that we have had difficulty with is parsing the captured output during the build process. Often we find stdout and stderr messages not being captured and viewable in the web interface. This usually results in "big stick" poking about to try to resolve the issue versus more targeted resolution that cleaner logs would allow.

We've really benefited from the Build Automation and CI/CD capabilities of Bamboo and it's integration with our Bitbucket and GitHub repositories. I recommend this for folks looking for a CI/CD solution.

We've seen a significant improvement in our ability to track and resolve build issues as well as managing build artifacts. Previously, we were relying on manual builds with moderate success. Being able to tie automation into our build process has really made a difference. We regularly utilize the "Latest Successful" build artifacts in our process and we've been able to avoid introducing errors on multiple occasions.

Bamboo has a painless installation process, helpful quick-start guide, simple build configuration, and seamless integration with JIRA. Bamboo supports builds in any programming language using any build tool, including Ant, Maven, Make, and any command-line tools. Polling strategy can be easily configured and scheduled. It comes with configuration templates like ANT, Bundler and so on.

Support provided is real good and integrates with other IDEs easily.

Does come with lesser plugins and its not very flexible. Bamboo is really limited for a modern day tool, that too for a CI tool, where things aren't done from scratch.

If you are already using Atlassian products like Jira, stash, Confluence etc, then it makes sense to use Bamboo. Bamboo will integrate closely with other products in Atlassian ecosystem.

Installation of java prior to setting up of bamboo is required, going through documentation could be helpful.

I required to a tool to ensure that whenever code is committed to the repository, new changes integrate well into the existing code base and build, unit tests and integration tests are performed. Bamboo did all this

Easily configurable for project granularity. For example, I can define the relevant git repository's branch to a build project/job, provide the necessary build tasks with lots of different executables and scripts, and segregate the build from the release stage with parallel jobs for only specific users or groups. Lots of popular language integrations with multiple notification methods and great integration with other Atlassian products.

Free only for first 7 days (as of June 25, 2015), although for only $10/mo for 10 jobs for 1 remote agent, it's a solid option for those ready to use enterprise-ready tools like Bamboo and its brothers and sisters of Atlassian products. I hope that there becomes a greater focus for mobile applications.

For enterprise ready Continuous Integration tool, Bamboo is a great choice paired with other Atlassian products.

Fast and contiguous partitioning of build and deployment tasks. Bamboo is a chiefly a continuous integration tool, but it does great in assisting with deployment issues and segregating build tasks to allow you to debug your code. Automated merging of branches is also a great feature.

The integrations with the other Atlassian tools (BitBucket, JIRA, and Confluence) work with no effort, right out of the box.

The ability to set fine-grain access control for the deployment phase for each target environment is great. As a public company, being subject to SOX compliance requirements means things such as segregation of duties (no developers deploying to PROD if the application can influence financial reporting). My developers have access to deploy via Bamboo to DEV, but a release engineer can only deploy to PROD.

The configuration of authentication against an LDAP source (such as AD) is a bit clunky compared to the other Atlassian tools. It requires you to configure the user directory source via config files without much direction compared to JIRA and Confluence which you can do it right in the web interface. Even myself being a CLI guy and coder, I would still prefer they were consistent with the other tools.

One big feature that Bamboo is missing is the ability to create a git tag after a successful build against trunk (which is basically a release candidate). Jenkins has this feature out of the box from what I have read. There isn't even a plugin available on the marketplace to do this.

One feature I wish it had is tight integration with Ansible for the deployment phase. Right now I just use a script task for deployment which calls the Ansible playbook to execute the complex, multi-tier deployment with rolling upgrades. Ansible requires SSH authN to the target nodes; if I use the out of the box SSH plugin in Bamboo, I can store the private key within Bamboo, even with a passphrase. If I run Ansible as a script task for the deployment, I can't use the SSH key/passphrase feature of bamboo.

The price is reasonable and well worth it if you already an Atlassian customer using their other tools and want the integration. Jenkins may be enough if you don't care about the integrations.

Consistent builds and automated deployment to all environments (DEV/UAT/PROD). Continuous Deployment in DEV, and push-button deployment in non-DEV by a release engineer (due to segregation of duties requirements). 0 manual steps required other than pushing the button for the deployment.

What I like best about Bamboo is the nice user interface and how easy it is to use and understand.

One thing that I think they could improve on is easier integration with other tools like HipTest.

I recommend you compare this product to other like it and decide what best works for you. I like that Bamboo is easy to use and looks nice from a user's point-of-view.

My company uses Bamboo to build upon commits to our Bitbucket repository, run unit tests and deploy to our various test, staging, and production environments. To have Bamboo build our projects after each commit and run the unit tests allows us to catch bugs early on to save time and money. This benefits our developers, QA analysts, and the company as a whole.

The #1 feature of Bamboo for me is the integration with the rest of the Atlassian suite of products. It's essentially a simple, one-click add-on to my current infrastructure, which consists of JIRA, Bitbucket & Confluence.

Setting up any number of build plans in Bamboo was super easy & quick, and integrating tests into those builds was also easy (and very useful). It helps us keep our manual QA costs down.

Also - as with all Atlassian products - it's cheap. :)

As with a lot of the Atlassian products (in my opinion), it's sometimes hard to get a good answer to questions for things. For example, i don't think the overall documentation online is the greatest - I don't always want to reach out to a support person for answers.

Getting build automation into our team's workflow was our main goal, but creating/automating tests was integral in freeing time that we were spending on manually QA'ing various parts of our applications.

- Can automate a wide variety of builds

- Easy to setup in aws

- Easily integrates with our on-prem servers

- Can be slow at times with how it integrates with our ldap service

- Restarts itself randomly at imes

- Autonomous deployments to dev/qa/prod

- Automation in migration feats such as svn -> git

This product is very easy to use and can easily be configured. The tool allows both developers, and non-developers insight into the currently deployed WAR file. We have many apps, each with various environments. Bamboo allows the QA team to easily deploy the desired code base.

The build plans seems 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,

Easy to configure

Easy to use

Clean UI

Easy permission controls

integrated with other Atlassian products such as JIRA

This tool allows the team to easily deploy to any environment in rapid time. It enables continuous delivery

easy to implement blue green enabling 0 down time

As with all Atlassian products, the best part of Bamboo is the integration into their full suite of software. Getting started with Bamboo from a Stash or Bitbucket code repo is as simple as clicking a button, and all downstream changes are immediately tracked and updated. Atlassian has made a huge effort to ensure that the dashboards to monitor build and deployment plans are both useful and informative, and it has paid off in a big way. Users can start, stop, change, monitor, create and delete plans from the push of a single button. Overall, Bamboo is great at:

* 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

After setting up several build and deployment plans using Bamboo, there are a few areas where this product could be improved:

* Documentation is hard to get to, and not always relevant to actual questions you may have about the product.

* A lot of the underworkings are a black box, which makes it difficult to work with.

* No clear right or wrong way to do things, despite being a enterprise product.

* Tasks cannot be put in if/else statements

* No good way to link successful builds to other builds

If you have already bought in to the Atlassian product suite, there is no better CI/CD product than Bamboo. However, make sure your entire team has training from Atlassian to understand how they will fit in the toolchain of your work, or else you run the risk of creating build plans that are detrimental to your future work.

Bamboo has completely changed the way that my team works, for the better. We used to rely heavily on stress testing and manual QA which was extremely time consuming and error-prone. Now, we are able to commit code and have automated deployments happen, and be assured that we are not breaking anything due to unit testing build into Bamboo. Our deployments have gone from once a week to several times per hour, letting our company be more agile in meeting our stakeholder demands.

Can assign build agents based on requirements

Granularity of build plans, branch builds, jobs and tasks provides a lot of flexibility

Drill down from a nice UI into a raw log file.

Really nice integrations with Atlassian products, especially JIRA and Stash. See the commit that is building and the story associated with that commit really easily.

The build monitors and HTML tags features are really useful, but any build system worth it's salt implements these.

The way it's configured, end users do not have admin rights to the build servers, and this causes endless difficulties.

Our company has so many products that it is very slow to load some pages because they have so many entries.

I've always found the deployments section hard to use, but this might just be because we use Bamboo with Nolio from CA, which is a terrible product.

The logs from the build servers can be really cryptic and hard to sift through. It is often hard for me to tell if the build is broken because the code I wrote is broken or because of a problem with the build server.

The biggest win is integrations with Atlassian products and managing deployments. Other than that, it doesn't do much more for you than something like Jenkins.

Building independently of local architecture on developer's machine, verifying code portability, deploying build artifacts from artifactory. Running Sonar static code analysis on a nightly basis, which calculates code coverage and complexity hotspots.

Bamboo is very reliable, and requires very little maintenance. Once workflows are configured, it just works.

Lack of progress on .net and Perforce support.

If you use Perforce be aware Bamboo does not support streams.

Increase the reliability of our software and development time with continuous integration. A central repository with build and test result history.

I used Bamboo and all the Atlassian stack to set up an ecommerce based on Magento. We were using the AWS stack and Bamboo was the best choice that I ever made.

The set up into a Amazon cloud is very good, the control panel is very clear and also the configuration was pretty straightforward. Managing Test servers and productions was very easy. Deploy into an AWS with multiple servers was very easy and the doc were very detailed.

The Setup of the first deploy task is not so intuitive, needs time to understand all the different options and how to use them. Amazon should publish screencast-doc only for developers to how to setup a basic deploy.

Very recommended. Try to hire a AWS certified Sysadmin to set up the system first.

We were using AWS stack and Altaissan Stack to set up an ecommerce based on Magento.

Bamboo was used to deploy on test servers and production automatically and did a great job.

I liked how it didn't force you to use a predefined IDE. I had the option to choose my IDE. Of course I went for Microsoft Visual Studio. During my time using bamboo, it was evident how they always have the developer in mind. They have great compatibility with source controls systems such as GIT and SVN.

I felt that the 7 days free trial was way too short. I started to like Bamboo way later. It is not the type of environments that you start to like the first time you use it.

Bamboo is a good option when you have to build multiple times and work with compiled programming languages. If you work with C# or Java(interpreted programming languages), then do not go for Bamboo.

We forced our VPS to multiple builds in very short time periods, and the lifespan of it was shortened. With Bamboo, we not only had the option for multiple and efficient builds, we had the capability to use source control revision systems(mainly git).

It's easy to use for easy things. Fortunately most of what I do is easy. It's harder to do harder things but in most cases it is possible to work within the constraints of the system. The documentation is pretty good once you figure out where it is. Support is excellent. I have used Bamboo for several years now and each time I have had to get Atlassian involved in a support issue they have been very helpful. Perhaps once, I've gotten a guy that I knew more than he did.

The bottom line is that if you can script it you can do it in Bamboo. Love the integration with JIRA and Fisheye.

The organization of the gui is meh. I have a lot of plans and spend much of my day scrolling down to find the build or deployment I need to engage. This is particularly true of deployments since there is no "project" grouping mechanism as there is in the build "side"of Bamboo. Deployments functionality is getting better though it still has room for improvement. The documentation on Deployments is still lacking to a degree and the REST API for deployments could improve. I'd like to see more ability to report on activity. How many builds did I do over all during the last x days. How many deployments did I do over the last X days. What is the break down by environment. Get a rest link to the last build log file (this may exist, but I haven't found it in the documentation yet).

I wish there was a mechanism for prompting users for variable values at runtime. And to display build execution instructions (or deployment instructions). These are the only things that is are real hindrances to me.

Set your expections and identify resources. Bamboo can do anything Jenkins can do as far as I know. You get the added integration benefits from other Atlassian tools. The tool isn't the thing though. It is the knowledge of your developers, configuration management users, and operation people who will make your Bamboo implementation successful. Bamboo at it's most basic is a scaffold onto which you add the pieces of your build. You still need to write the scripts that make the objects move around the network. You have to know how to build your application and how to translate those instructions to the plugins that you use in Bamboo.

Build and deploy.

Prior to moving to Subversion from ClearCase and from a manual (somewhat scripted) build process to Bamboo the build process was exceedingly long and difficult. We've sliced the build from 3-5 hours to fifteen minutes in most big projects.

can integrate with Jira and stash seamless.

can manage artifacts and deployment targets (environment)

can manage the version of each release.

not open sourced.

Does not have a large community to provide plugins like jenkins.

sometime they are slow to fix some bugs.

if you are tired to choose plugins for Jenkins for features that are not buildin. Try Bamboo, it will give you a peace mind.

Build and deploy.

we switch from jenkins to bamboo for it's better integration with stash.

and the agents can be installed on remote network (behind firewall) to do the deployment jobs!!!

Great integration with JIRA and confluence,

Ease to sea reports,

Notifications and failure reports

Easy to create multiple plans, build integration and que

well integration with GIT

UI can be more simpler,

Logs displayed can be more intutive, should have filters and good log viewer

Make sure you setup correct email triggers else you can be spammed by bamboo email triggers,

Great tool, make sure to intigrate with JIRA and confluence.

We had multiple teams working on the the same code base so we wanted a good CI and well defined plans and triggers to make sure bad code is not commited,

Bamboo helped us to execute the build on specific triggers making sure they are compliant

Easy to setup by adding different projects. This product is modularized, you can configure the product many ways as you want. Lots of plugin support. Versatile. Excellent CI support

It is very sluggish to load pages because they have so many entries.

Turns buggy if more traffic flows in.

There is no way to link other builds to other builds

CI workflow. This product helps us obtaining our continuous integration and delivery goal.

Bamboo integrates very nicely with the rest of the Atlassian Suite of products such as FishEye and Crucible. It's also very easy to use. I am predominately a developer and not a scrum master or maintainer of the Atlassian projects in my company's role. However, I can easily go into the Bamboo console and start off a build manually if I need to.

While it can be a free product, it is only free for minimal functionality. After that there is a charge.

There is a lot more that Bamboo can offer than what I described in my review. I would recommend reading more into the documentation provided by Atlassian to get the most out of the product.

If you don't know if you would find Bamboo useful, they do have a free trial version that allows you try some of the features before signing up for a paid tier.

Bamboo allows us to set up scheduled builds that occur at a particular time in the middle of the night (as to not disturb any developers that are testing against a particular server). This has automated the build process and saved us a lot of time when testing new builds. We get detailed logs and information when a particular build fails.

Really nice integrations with Atlassian products, especially with JIRA and Bitbucket Server.

Offers an intuitive UI.

Bamboo supports builds in any programming language using Ant, Maven, Make etc.

It's cheap.

Documentation is hard to get to.

The logs from the build servers can be really cryptic.

Does not have a large community to provide plugins like jenkins.

Build and deploy, this product helps us obtaining our continuous integration and delivery goal.

super integration with JIRA and other confluence products, easy to deploy and manage

Notifications can be better, more options to be made available to end users to let them know how to do it.

make sure to use it with other atlasian products

We had multiple teams working together on a huge application, so CI builds made sure faster development and testing

Clean UI, good high-level job monitoring. Very responsive actions, no hiccups or freezes.

A little confusing getting to a specific running job from the main job list, I often find myself looking at the previously-completed job instead of the currently running one.

If you are on Github, don't bother -- Go with Travis.

We use Bamboo for all of our continuous deployment. It's a simple way to build specific environments when we push to specific branches.

Bamboo is easy to setup by adding different project and plans. It also scales up well to manage multiple build agents. The Jira integration is a nice bonus.

Although apparently simple on the surface, the UI is actually quite tricky to navigate. I found that there's quite a deep level of nesting of settings.

Evaluate whether this solves your needs or whether Jenkins might also achieve that. Bamboo is a good choice if you already have Atlassian products in your stack.

Bamboo helps us achieve our continuous integration and delivery goals in a convenient manner.

Works really well and shows the problem very efficiently

Everything works as intended, I haven't had a issue worth reporting

This is really a great product. We also use all the other atlassian products so we may have some bias

We have noticed this will compile the necessary files correctly and let us know if someone added a custom label in salesforce without putting it in the package.xml and will show an error without deploying from our dev environment to our test environment

It performs continuous integration and it's better than TeamCity. Some of the reporting features are Nice and it integrates quickly with Jira for PM tools.

I haven't used it in a while but the GitHub integration was not very good and overall for a paid product there are much better free or cheaper resources out there.

Use Travis CI. It's easier and cheaper and has a lot better integrations with GitHub or even Hosted GitHub.

Continuous Integration for a suite of apps developed in house, running on Git.

YOU CAN TRACK YOUR HOURS WORKED AND ASK FOR VACATION DAYS. ITS ALL CALCULATED!

NOTHING. I REALLY LIKE THE PROGRAM. IT DOES THE WORK AND IS EASY TO USE.

BEST PROGRAM EVER TO TRACK EMPLOYEES

QUICK RESPONSE RATE FROM THE COMPANY

It was easy to implement. However not very intuitive to start with.

Difficult to start. Did not deal with large processes in an efficient manner. Performance issues.

Make sure to use it thoroughly before purchasing it. You don't know if it meets the requirement until you use for few business processes

Used it for Workflows for internal and external vendor approvals

Tight integration with Jira and Stash

Branching and pull requests

Bland user interface, poor dashboards and user feedback.

If you use JIra or Stash this is the product for you.

It allows us to have a feature branching model and improve software quality.