BitbucketCloud Project Binding

[janfschmidt (Jan-Frederik Schmidt)]

I would like to set up project binding between Bitbucket Cloud and SonarCloud via the API. Unfortunately, this feature does not seem to be implemented (yet?).

Specifically, the API route is

POST https://sonarcloud.io/integration/bitbucketcloud/bind_repo

with the payload

{"jwt": "...", "projectKey": "PROJECT_KEY_HERE"}

Unluckily, the normal SonarCloud token can’t be used for this request either, it seems to be a special token in the Bitbucket context.

Can you tell me if it is possible in the (near) future to implement this route or alternatively tell me about which way I can generate a JWT for this request?

What i found so far is

How do I script linking a SonarCloud project to a Bitbucket Cloud repo

I already programmatically create new sonar projects with the REST API: https://sonarcloud.io/api/projects/create Im setting all these values in the scanner command. everything works except it looks like I still have to link it to the BB repo to get the widget? // sonar project key /k:“mykey” // project name- human readable project name that appears in the UI /n:“myproject” // scan version /v:“myversion” // sonarcloud token /d:sonar.login=“mytoken” // sonarcloud org /o:“bitbucketTeam” …

but it doesn’t work for me.

[janos2 (Janos)]

@janfschmidt

I would like to set up project binding between Bitbucket Cloud and SonarCloud via the API. Unfortunately, this feature does not seem to be implemented (yet?).

Specifically, the API route is

POST https://sonarcloud.io/integration/bitbucketcloud/bind_repo

Note that the endpoint you found is not listed in the official API documentation.

The recommended way to bind Bitbucket projects today is still to use the UI. (Import org, import projects.)

It could be a good idea to describe your use case to do this programmatically, so that it might gain interest and traction.

[janfschmidt (Jan-Frederik Schmidt)]

My use case is relatively simple to explain: In my company we have a large amount of repositories that I programmatically manage across multiple services (BitBucket, CI/CD, SonarCloud, …). Say: As soon as a new repo is added or something changes to an existing one, in all services the changes are automatically applied. I already create and manage the projects in SonarCloud via the API (more precisely via the Python API). Now, if for example a repo changes (rename, etc), I would like to be able to manage the binding between SonarCloud and Bitbucket also via the API.

[janos2 (Janos)]

@janfschmidt

Now, if for example a repo changes (rename, etc), I would like to be able to manage the binding between SonarCloud and Bitbucket also via the API.

Hm, I think that repo renaming is not a good example here. The binding is based on repo id, so it shouldn’t be affected by renaming of the repo. So, why do you think it’s necessary to update the binding when the repo is renamed? Or do you have another kind of example (not renaming)?

[janfschmidt (Jan-Frederik Schmidt)]

My mistake, I did not give all the information: I always keep repo names and project key in a consistent format.So if I rename a repo, the project key changes too and so the binding has to be renewed.

[janos2 (Janos)]

If you want to update the project key on SonarCloud side to match the change on Bitbucket, you could use the api/projects/update_key official API endpoint. I don’t see a need to update the binding.

[janfschmidt (Jan-Frederik Schmidt)]

I already use the route. To be honest I just can’t remember what exactly I did to make me renew the binding, but I definitely had a use case for it

[janfschmidt (Jan-Frederik Schmidt)]

Ha, today I remembered the reason (Ok, admittedly the problem has come up again ): When I create a new BitBucket repository and set up a SonarCloud analysis in my pipeline, the PRs are created but not displayed in BitBucket because the project is not even linked to SonarCloud yet.

[Colin]

Hey @janfschmidt

You might be interested in this comment (and the roadmap item linked)

Azure Devops projects are not binding in Sonarcloud

Hey there. I know “It’s the way it always has been” isn’t a great answer, but it’s probably the truth here. A lot happens in the backend when you bind the project through the UI and it has never trickled down to the scanner, nor any effort put into connecting the dots once the first scan of a project has been published. We also have generally come from the opinion that project provisioning from the scanner is allowed but not ideal, as it can cause the proliferation of many projects where admin…

[janfschmidt (Jan-Frederik Schmidt)]

This is very unsatisfying, especially since an API route can also control “complex” backend tasks very well - if it works via the UI (especially since an internal API route is already being called), it should also work via the external API. I really hope that the feature will be implemented soon.