When creating/updating a linked repository or a plan specific repository that is referencing a BitBucket Cloud repository a 404 is returned when the BitBucket Cloud users or teams API is called.
2020-04-13 12:13:15,778 WARN [http-nio-8085-exec-18] [RESTCall] Response from GET https://api.bitbucket.org/2.0/users/mikerudat/ (404)
2020-04-13 12:13:15,778 ERROR [http-nio-8085-exec-18] [BitbucketApiServiceImpl]
com.opensymphony.webwork.dispatcher.json.JSONException: JSONObject["uuid"] not found.
at com.opensymphony.webwork.dispatcher.json.JSONObject.get(JSONObject.java:419)
at com.opensymphony.webwork.dispatcher.json.JSONObject.getString(JSONObject.java:590)
at com.atlassian.bamboo.plugins.bitbucket.impl.BitbucketApiServiceImpl.getUuidForUserOrTeam(BitbucketApiServiceImpl.java:319)
at com.atlassian.bamboo.plugins.bitbucket.impl.BitbucketApiServiceImpl.getUuidForAnEmailOrUsername(BitbucketApiServiceImpl.java:218)
at com.atlassian.bamboo.plugins.bitbucket.v2.configurator.BitbucketCloudServerConfigurator.validateUsername(BitbucketCloudServerConfigurator.java:456)
at com.atlassian.bamboo.plugins.bitbucket.v2.configurator.BitbucketCloudServerConfigurator.validateUsernamePasswordCredentials(BitbucketCloudServerConfigurator.java:374)
at com.atlassian.bamboo.plugins.bitbucket.v2.configurator.BitbucketCloudServerConfigurator.validate(BitbucketCloudServerConfigurator.java:271)
at com.atlassian.bamboo.plugins.bitbucket.v2.configurator.BitbucketCloudServerConfigurator.validateForConnectionTesting(BitbucketCloudServerConfigurator.java:292)
at com.atlassian.bamboo.configuration.repository.VcsConfigurationHelperImpl.validateVcsConfigurationForConnectionTesting(VcsConfigurationHelperImpl.java:125)
The username is being passed vs the UUID of the account for the user. It appears the API call passing the username has been inactivated due to GDPR and the UUID should now be used in Bamboo.
Issuing a curl command against the endpoint does succeed when passing the UUID
curl https://api.bitbucket.org/2.0/users/%7B114aa7e6-a24f-4b58-be59-7620706c07b2%7D
We are using Bamboo 7.0.2
Thank You,
Mike
Hi, the same bug is contained in version 6.10.3. Is it fixed in 6.10.5?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
same issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are encountering the issue as well in version 6.9.1.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Look at https://jira.atlassian.com/browse/BAM-20900, I've not yet tried the workaround
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Awesome, the workaround was successful. I added
JVM_SUPPORT_RECOMMENDED_ARGS="-Dbamboo.bitbucket.cloud.use.workspace.api=true"
to bin/setenv.sh for our linux installation. Thank You!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
does the fix work on version 6.9.1?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.