Private bitbucket repo push should trigger Bamboo build
Asked by Viktor Nagy:

I've set up a Bamboo hook on my private Bitbucket repo. But, no matter my pushes to bitbucket, it never triggers a build.

What settings should I change and how?


Answers:
author: Viktor Nagy
body: I've managed to get this working, just the Bitbucket IP addresses I've found were wrong. The correct IP addresses to allow the trigger are

* 131.103.20.165
* 131.103.20.166

(these come from an Atlassian Support answer, and they work fine now)

comments: author: aMarcus
body: For others finding this request, these IP addresses are noted in our [documentation](https://confluence.atlassian.com/x/GQF3F). We keep it up to date when IPs change.


author: Sam Kenny
body: I am seeing a similar problem. Bitbucket is not triggering builds in Bamboo on push. If Bamboo polls Bitbucket it works fine. I entered the IP addresses above (and 131.103.20.168) but still no joy.

I will raise this with support but wanted to post here in case other people experienced the same problem.


author: aMarcus
body: For Bamboo hook issues, please come to support and report the specific details so we can look. Once we know the issue, we'll update this post with the correct answer.


author: Kevin Gorham
body: We're seeing the same problem. We have the hosted version of Bamboo and I've set up a Bamboo hook in my bitbucket repo, following all the steps in the documentation and it is not working. My username/pass/url/planKey are all correct.

However, when I create a POST hook configured to post to a URL with the following format, it works and I see builds triggered after commits:

https://\[hostedAccountName\].atlassian.net/builds/updateAndBuild.action?buildKey=\[planKey\]

<br />

Of course, this doesn't allow me to use any of the "advanced trigger options." Also, when I setup a Jenkins hook, it works just fine. You would think that hooks for bamboo would work seamlessly.

Is there at least some way to [test Bamboo hooks](https://bitbucket.org/site/master/issue/4667/add-ability-to-test-services-bb-5436) on Hosted instances? If I could just see the logs for the attempted hook, I could probably fix the problem.


author: Thaddeus Batt
body: There's a bug report logged re. the Jenkins hooks here: [](https://bitbucket.org/site/master/issue/9196/jenkins-hooks-not-working)<https://bitbucket.org/site/master/issue/9196/jenkins-hooks-not-working>


author: aMarcus
body: EDIT: We've found an issue with the Jenkins broker and are deploying a fix now. For other issues, please come to support as each Hook works differently.

Previous reply: We haven't made any changes to our Hooks nor have we had any specific reports other than this particular post. Please come to support with the specific details and we'll give you both a hand.

comments: author: aMarcus
body: The Jenkins hook has been fixed.


author: Thaddeus Batt
body: We are seeeing the same problem with Jenkins hooks. We have several projects in bitbucket with jenkins hooks in place that have been working for months and recently builds are no longer being triggered by commits.


author: Viktor Nagy
body: A small note. The affected bitbucket branches are set up under Bamboo, and I can build them fine with a daily build "trigger" or manually, just not automatically after a git push.


Tags: bitbucket-cloud

cloud