Bamboo "Bitbucket server repository triggered" trigger stopped working on upgrade

I previously had the Bitbucket trigger working properly, but after upgrading Bitbucket from 4.3.0 to 4.6.1 and Bamboo from 5.10.0 to 5.11.3, commits are no longer triggering builds.

I've checked the logs for any errors, but nothing is showing up.  I have disabled and reenabled the authentication on the application link (on both sides) and that seems to have helped, but I'm not sure why it happened or if it will happen again.

5 answers

Having the same issue... The Bitbucket commit trigger seems really really shaky !

And, it has happened again, none of my triggers seem to be hitting.  Perhaps reinitializing the link caused it to build once, but now it's not running.

I was able to get things back to normal, by rebooting Bamboo, and then Bitbucket. Maybe there is some implicit order, of which the application links need to start up ?!.




Is there any solution to this issue? I am having the same issue.

Any Atlassian guys with proper answer?

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,765 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you