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.
Hi there,
We suddenly have issues connecting to our Git repositories sitting on BitBucket. We get the following message when we test the connection: "We couldn't connect to the repository. The details you provided were invalid.". Strangely enough, the drop-down menu does show an up-to-date list of available branches.
We use username/password as credentials, not SSH keys. We've deleted the cache for the repo we were considering in particular, to no avail.
If we add the repo through 'Add repo' / 'Git' (not BitBucket), the connection is fine.
Our plans used to work, we haven't modified them. The only recent change is a Bamboo upgrade (self-hosted) to version 6.9.0.
Any ideas? Thanks in advance
Hi @Christophe L., @Renato Guimaraes
Thanks for reaching out to the Atlassian Community!
The issue that you are reporting looks to be related to changes to the Bitbucket Cloud APIs that went live on June 11, 2019. As many of these changes were needed to comply with GDPR, and protect our customer data, the changes went live as quickly as possible. Bamboo versions 6.8.3 and 6.9.1 were released to fix these issues, meaning that you will need to upgrade immediately.
Some background
The Bitbucket Cloud REST API v1 was removed, and API v2 endpoints were updated to comply with GDPR privacy regulations. Part of these updates removed a variable containing information that Bamboo expects in the JSON response from Bitbucket.
This change resulted in the creation or editing of Linked repositories of type “Bitbucket Cloud” failing with 401 (Unauthorized) exceptions. You may see "Resource removed" or “Invalid username” error messages in the Bamboo UI as well as the message you mentioned.
For more information on the "Resource removed" issue, please see our public bug report here:
For more information on the GDPR related changes, please see:
Workaround
If you are unable to upgrade right away, as a workaround, we recommend creating Linked repositories of type Git or Mercurial to connect to your Bitbucket Cloud repositories.
I sincerely apologize for any inconvenience this may have caused. Please let us know if you have any questions or concerns.
Thanks,
Elias | Bamboo Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.