You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I just spent quite a few hours trying to integrate BitBucket and Azure DevOps. We were only able to list repos, and all other operations/selections would not work and would provide a 'Forbidden' error.
We attempted to work around auth issues (MFA enabled on BitBucket), but there doesn't seem to be any way get a private key into Azure DevOps to allow for the jobs to authenticate to build out pipelines.
It doesn't seem to be possible....has anyone had experience with this and found a workaround?
@Ziggy Where did you white list the IP? I am having this exact issue and it is driving me insane. Going on almost a whole day trying to troubleshoot this problem.
Are you hosting your own BitBucket Server or using Cloud Hosted?
Found this for the IPs of Azure Devops
Thank you
- Marco
Hey @[deleted] , we whitelisted it on the Bitbucket Cloud Hosted solution itself under Access Controls for the account.
Just FYI, after much more discovery work, even though I was able to list the buckets and select content, we were still unable to perform a build. A git checkout from Azure DevOps was failing to perform the activity while complaining about whitelisting.
In that case, Microsoft told us to either whitelist the entirety of the Azure CIDR ranges, or move on to self-hosted build agents.
I hope this helps! Cheers!
Thanks @Ziggy Yeah I am trying to create a Build Pipeline and when I hit save getting the Forbidden error. I'll put the IPs in the white list and see what happens. Thanks for the quick response.
Thanks