Bamboo service management

With this service, you can integrate Bitbucket Cloud with Bamboo, an extendable enterprise continuous integration server. This service will force a Bamboo manual build when a commit is pushed to your repository. Note that this will override any conditions for branches or file exclusions.

If you are having trouble with the service, see Troubleshoot Bitbucket Cloud services.

Setting up the service

 You must have administrative access on a repository to add this service.

  1. Go to the repository's settings.
  2. Click Services in the left-hand navigation.
    The Services page appears.
  3. Select the Bamboo service from the services dropdown.
  4. Click Add service.
    A new section appears for the Bamboo service.
  5. Enter the following information:

    Field Description

    Enter your Bamboo user password.

    If you use Google Apps with Cloud to make the Bamboo Service work, you must configure this service using your Cloud username and password: not your GoogleApps credentials. For information on resetting your Cloud password, see this page. this page.

    Username Enter your Bamboo username, this is the user that triggers the build
    Plan Key Enter the Bamboo plan key (ex. BB-STAGING). The plan key can be found in the URL of any page of a plan.

    Enter the URL to your Bamboo instance (ex. 

    For Atlassian Cloud, the URL is 



  6. Click Save.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

21 Archived comments

  1. User avatar


    Does not work with plan branches. The main plan is always triggered instead...

    18 Jan 2013
    1. User avatar

      Fabian Fülling

      Is there no way to use the Bamboo hook with plan branches? Then it's pretty useless, isn't it?

      01 Nov 2014
    1. User avatar

      Justin Montgomery

      Currently we use repository polling to trigger builds on our main plan and branch plans. Does this mean I can't switch to this service manager, or any kind of webhook really, since it won't work with our plan branches?

      04 Aug 2015
  2. User avatar

    Mark Snelling

    This requires a Bamboo user to work. Wouldn't it be better to use the Trusted Application Links method like JIRA, Confluence etc?

    25 Jan 2013
  3. User avatar


    Where do I get the PLAN KEY, very frustrating, I've been looking and searching everywhere. Found old docs referencing PLAN KEY is in Plan Details tab, but Bamboo On-demand, this was removed (?!) from the Plan Details tab.

    Next question, Why take it out in the first place?

    Confusing and misleading.

    15 Apr 2013
    1. User avatar

      Marcus Bertrand [Atlassian]

      Thanks for pointing out that we didn't mention the location of the plan key. We've updated the page to reflect the correct location. If you want to see something changed in Bamboo, please visit and file an issue under the Bamboo project.

      15 Apr 2013
  4. User avatar


    We're accessing Bamboo with Google Authentication. I'm trying to set up a Bamboo service which will trigger a build in Bamboo.

    I've tried following this guide - and I'm not able to complete that as I don't have a password for Bamboo.

    Can you give me some directions about what I should do?

    11 Jul 2013
    1. User avatar


      You should be able to enter the same username password as you use to log into Bamboo. So like and foobar. Did you try that?

      11 Jul 2013
  5. User avatar

    Mark Snelling

    My comment above about using the Trusted Links mechanism is important for us users of Bamboo Ondemand which charges per user, we shouldn't have to add another user just to automatically trigger Bamboo builds.

    We have our Bamboo instance set up to poll BitBucket, so I guess it's Atlassian's infrastructure taking the hit with all the polling.

    12 Jul 2013
  6. User avatar

    Anthony Archer

    Using this approach, the builds always show up as Manual Builds.  I see someone else ran into the same issue, BAM-13034 - Builds triggered by Bitbucket are wrongly marked as manual builds. Open

    05 Sep 2013
    1. User avatar

      Marcus Bertrand [Atlassian]

      I've updated the language of this document to explain this behavior. We will be working on a new hook soon to use the updateAndBuild.action alternative.

      05 Sep 2013
      1. User avatar

        Ricardo Correa

        Is there any way to follow the status of this issue? It's been annoying me as well.

        20 Sep 2013
        1. User avatar

          Marcus Bertrand [Atlassian]

          Sure. Follow this issue on Bitbucket's public issue tracker:

          20 Sep 2013
  7. User avatar

    Ben Tatham

    Does Bamboo support regex on the plan key in the api used by bitbucket?  This feature would be nice as well.

    07 Oct 2013
    1. User avatar


      Ben, I'm not sure what Bamboo supports on the plan key.  The product does support regular expressions elsewhere. 

      07 Oct 2013
  8. User avatar

    Christian Jensen

    I am not getting any triggers in Bamboo. Is there a log somewhere that I can see what is going on?

    Some form of self diagnostic would go a long way here. How do I test the hook and see the result?

    22 May 2014
    1. User avatar

      Marcus Bertrand [Atlassian]

      We don't surface our logs externally, but we do have them. Please open a support request with the repo url and we'll take a look.

      23 May 2014
  9. User avatar

    Rishi Goel

    I followed this article but I am not getting any builds triggered automatically when a commit is made. Are there any other configurations which need to be done?

    25 Sep 2014
  10. User avatar

    Christian Jensen

    Trailing slash is important in the URL:

  <<< wrong <<< right

    17 Dec 2014
    1. User avatar

      Dan Stevens [Atlassian]

      Thanks Christian. I've fixed that.

      17 Dec 2014
  11. User avatar

    Seth Reeser

    GitHub's Bamboo Service supports the a compound build key (plan key in Bitbucket speak), I do not see anything about this for Bitbucket's Bamboo Service. This makes building separate environments impossible.

    1. "build_key" is the identifier of the plan you want to trigger
      Example: "BAM-TRUNK", where BAM = project key, TRUNK = plan key

      A compound build key value can be used to specify multiple builds or associate
      specific branches with a build
      Example: "master:BAM-TRUNK,3-2-patches:BAM-32PATCH,BAM-TESTS", where BAM-TRUNK
      will be triggered only by pushes to the master branch, BAM-32PATCH will only
      be triggered by pushes to the 3-2-patches branch, and BAM-TESTS will be triggered
      for any push.

    24 Jul 2015
Powered by Confluence and Scroll Viewport