Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

error adding bitbucket cloud repo to bamboo 7.0.2

Adam Caldwell April 27, 2020

We're getting an error: We couldn't connect to the repository. The details you provided were invalid.

We recently upgraded to bamboo 7.0.2 (from bamboo 5 -- with an intermediate step of upgrading to bamboo 6 so that we could upgrade without losing config -- primarily because we couldn't add new repos to bamboo 5).

The account is already used to access a bunch of repos on bitbucket cloud, so the credentials are correct.  In the atlassian-bamboo.log we're seeing:

2020-04-27 11:31:49,837 WARN [http-nio-8085-exec-5] [RESTCall] Response from GET https://api.bitbucket.org/2.0/teams/xxxxxxx@yyyyyyyy.com/ (404)

 

(where xxxxx and yyyyy are valid values).

 

When i go to that URL with a private browser, I get the same 404 error with a message of "xxxxxxx@yyyyyyyy.com is not a team account".

 

If I then go to https://api.bitbucket.org/2.0/teams/ and enter the xxxxxxx@yyyyyyyy.com and password when prompted and go back to the GET https://api.bitbucket.org/2.0/teams/xxxxxxx@yyyyyyyy.com/ URL, I get a response that shows:

 

{"display_name": "yyyyyyyyyy Build Admin", "uuid": "{b896cefd-748b-4480-b787-ZZZZZZZZZZZ ....}

(where i've anonymized the last portion of the UUID and left out the remainder of the request).

 

This seems like some sort of bug in bamboo 7.0.2.

 

We host our own bamboo server and use bitbucket cloud.

1 answer

1 accepted

0 votes
Answer accepted
Adam Caldwell April 27, 2020

Added:

JVM_SUPPORT_RECOMMENDED_ARGS="$JVM_SUPPORT_RECOMMENDED_ARGS -Dbamboo.bitbucket.cloud.use.workspace.api=true"

to bin/setenv.sh and restarted and it fixed it.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events