Continuous delivery from code to deployment

Bamboo is a continuous integration and delivery tool that ties automated builds, tests and releases together in a single workflow. It works great alongside JIRA Software and Bitbucket providing a fully traceable deployment pipeline. 

Build Results

Pricing overview

1 agent

10 Jobs $10/mo

1 agent

Unlimited jobs $50/mo

5 agents

Unlimited jobs $100/mo

10 agents

Unlimited jobs $250/mo

25 agents

Unlimited jobs $500/mo

100 agents

Unlimited jobs $1,000/mo

10 Jobs

on local agents $10 Starter

1 agent

Unlimited jobs $800

5 agents

Unlimited jobs $2,200

10 agents

Unlimited jobs $4,000

25 agents

Unlimited jobs $8,000

100 agents

Unlimited jobs $16,000
View full pricing details»


Highlight reel

  • Deployment Projects
  • build pipelines
  • Git
  • JIRA Software integration
  • better CI/CD
Bamboo for continuous delivery

Continuous delivery, unleashed

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. You can connect to your own S3 Amazon bucket and use the bundled AWS CodeDeploy task to deploy. Need to bundle your application in a container? Use Docker tasks. There are agent images to grab, and tasks to let you create your own image, run a container or push an image to a registry.

If connecting with Bitbucket and JIRA Software, details like JIRA issues, commits, reviews and approvals follow each release of your application from development to production.

Bamboo for continuous delivery

Get fast feedback

Define a stage of your build pipeline for compilation and unit tests, then move on to separate stages for longer-running integration, UI, and load tests. Tests in each stage can be run in parallel batches, discovering failures and getting feedback to developers fast.

Bamboo for continuous delivery

Painless CI on dev branches

Bamboo alleviates the pain found at the intersection of continuous integration (CI) and distributed version control systems like Git and Mercurial. New branches are automatically brought under the same CI scheme as master, and any two branches in the repo can be merged automatically before each test run. 

Bamboo JIRA Integration, development panel

Plan, track, build, deliver

Extend issue tracking into the realm of continuous delivery when you connect Bamboo to JIRA Software. View builds and deployment status right from the deployment panel in every issue. Defects against failed tests are raised directly from Bamboo so you can make the progress towards a release visible to everyone on your team.

Bamboo JIRA Integration, development panel

Up your game

Software teams in every industry are upgrading their continuous delivery pipeline with Bamboo. Easy build import from popular open source tools, user and group import from JIRA, seamless integration with Stash, and native support for Git, Hg, and SVN means you'll be building and deploying like a champ.


  • Tech Stack
  • Build Tasks
  • Triggers
  • Adaptability
  • building at scale
build technologies

Freedom to innovate

Bamboo is suitable for any language, and other popular technologies like AWS CodeDeply, Docker, Amazon S3 buckets, Maven, Ant, Git, Mercurial, and SVN. Support for loads more technologies like Heroku and Grails are available as free add-ons. Bamboo grows with you as your technology stack evolves.

reorder build steps

Drag-and-drop configuration

Take full control over the order in which build steps are executed. Need to grab code from a Git repo, then call Maven, then run a script before running a Docker container? No problem. Bamboo lets you do all of that inside a single job. Simply define your build tasks, then drag and drop them into the right order.

Multiple build triggers

Your builds, your way

Bamboo can trigger builds based on changes detected in the repository, push notifications from Stash, a set schedule, the completion of another build, or any combination thereof. Branch builds inherit the main code line's triggers by default, and can be customized on a per-branch basis. Bamboo can even pause at specific stages of a build pipeline – one click from you, and the build proceeds. 

customized builds

One-off customizations

Sometimes you need a little more power. Re-run builds to see if a test failure was legitimate or just flakey. Build against an arbitrary revision to isolate changes when debugging. Override a build variable's value this time, and automatically revert back to the saved value afterwards. 

large-scale build projects

Show admins the love

Repositories, build variables, user permissions, and notifications shared across builds means less configuration and more automation. Global default values for any of these can be fine-tuned for each build plan, and tuned even further for the plan's branches. 

Start a free trial of Bamboo

Try it


  • CI on the Branch
  • Prevent drift
  • Quarantine
  • testing at scale
CI on dev branches

Bring testing to dev branches

Adopting feature branching or a branch-per-issue workflow doesn't mean sacrificing code quality. Bamboo detects new branches in Git, Mercurial, and SVN repos, then automatically applies the main line's CI scheme to them. Use the branch builds straight away, or customize their triggers, variables, and notification settings. 

automatically merge after successful builds

Painless, automated merges

Each time a branch build is triggered, Bamboo can automatically merge it with the latest changes from master, then run your full CI scheme against the merged code. If the build is clean, the merged code can optionally be pushed to your branch automatically so you don't drift from the rest of your team. Or, push the merge to master to share your changes with the team and keep dependency bottlenecks at bay.

test quarantine

Keep the build green

Don't let red builds become the norm. Keep flakey or broken tests out of sight (but not out of mind), and keep the build green with one-click quarantine. Bamboo will continue to run quarantined tests and display them prominently in each build results. When you're ready, one more click unleashes them back into your build "for real."

parallel testing

Run tests in parallel

Bamboo supports up to 100 remote build agents, giving you the power to run batches of tests in parallel, keep the queue flowing, and get feedback to developers quickly. Agents can be configured with any technology stack you choose, providing the opportunity to test against all the different operating systems and browsers your customers use. 


  • Dev + Ops
  • Visibility
  • Tracking
  • Permissions
Bamboo for continuous delivery

Better automation for releases

Bamboo gives deployments the first-class treatment. Set up CI builds as normal, and feed the resulting build artifacts into deployment projects. Combine home-grown scripts, smoke tests, and third-party technologies like Websphere to define the deployment steps for each environment. Integration with Amazon S3, ready-to-use Docker agents and AWS CodeDeploy and Docker tasks make the deployment process faster and easier.

Deployments can be triggered automatically when a test run completes, on a schedule, or ad-hoc with manual triggers. 

Bamboo for continuous delivery

Know what's changing

Before deploying a new release, see the full roll-up of code changes and JIRA issues that have come in since the previous deploy. Ops teams can anticipate what they'll be responsible for deploying and supporting in production, and release managers get a clear view of what is going live. 

Bamboo for continuous delivery

From code to customer

A single screen in Bamboo brings together all the details around release candidates. Which environments has it been promoted to? When did the deploys happen? How were they triggered? What tests were run against the changes?

And for the ultimate in efficiency, the release's deploy status for each environment is displayed right inside issues when Bamboo is linked to JIRA.

Bamboo for continuous delivery

Dev speed meets control

With per-environment permissions, developers and QA can deploy to their own environments on demand while production stays locked down. Build engineers and ops teams spend less time servicing deploy requests, and one more bottleneck bites the dust.


  • JIRA Issue Links
  • Issue Creation
  • Repository Integration
  • Add-ons
Bamboo for continuous delivery

Get more out of JIRA Software

Bamboo offers extensive and ever-expanding integration with JIRA Software that other build servers can't match. Project managers, developers, testers and sys admins get actionable information, seamlessly!

You can link issues to dev branches to see real-time build status inside the issue, get related build results inside issues and the issue's vital stats on the build result in Bamboo, track each issue's deployment status throughout your environments, and see a roll-up of all the JIRA Software issues and commits included in each release candidate.

Bamboo for continuous delivery

Your team's new shortcut

Whether filing a deploy request for a successful build or raising a defect to track problems, creating JIRA issues from build results saves time and eliminates context-switching. When multiple tests fail, Bamboo lets you create individual issues for each test, or one bug to track the whole group. All issues created this way include a link to the associated build.

Bamboo for continuous delivery

See the context around builds

Bamboo hooks into repositories in Bitbucket and FishEye, tying builds to the code changes they contain. Commit messages, authors, reference numbers, and dates are displayed in each build result. One click takes you to the repository viewer to see diffs, history, and browse related code. You can even see branch build status when viewing pull requests and commits in Bitbucket.

Bamboo for continuous delivery

Make it your own

With over 100 add-ons, Bamboo can be quickly customized to suit almost any use case. Don't see the add-on you need? Build your own using the open REST API. Our developer docs include tutorials for building custom build tasks, and more.

Get started

  • Jenkins Importer
  • Helpful Resources
  • "What is CI/CD anyway?"
Bamboo for continuous delivery

Get started quickly

Teams migrating from Jenkins can import builds into Bamboo, slashing the transition time. Build engineers have better things to do than recreate configs click by tedious click.

Get the Jenkins vs. Bamboo lowdown here

Bamboo for continuous delivery

Continuous learning

With a variety of training, best practices, and support resources, help is never far away. Our quick-start guide steps through Bamboo's build structure and how to use it optimally. Get product announcements, tips, and tricks on the Atlassian blogHelp docs are available online, including notes from the dev team about each release. And Atlassian Answers, our Q&A forum, digs deeper into use cases and troubleshooting. 

As will all Atlassian products, Bamboo comes with access to our legendary support team – file a ticket and they'll get back to you fast.

Bamboo for continuous delivery

Glad you asked!

Continuous integration, or CI, is the practice of building and testing source code frequently. This provides rapid feedback to developers about their changes, and isolates commits for easy troubleshooting when the build fails.

Continuous delivery extends CI by automatically deploying qualified builds to testing environments. Releases to the customer happen only when the team decides it's time.

Bamboo is designed to make both CI and CD easy to set up. Keep your builds connected to code repositories and JIRA issues, and visible to the entire product team. Connect to your Amazon S3 bucket, and use Docker and AWS CodeDeply tasks for a seamless delivery pipeline.

Start a free trial of Bamboo

Try it

Latest Bamboo blog

No data found in this feed at the moment. Come back little bit later and try again.

Read more at the Bamboo Blog