I’m currently unable to create a mono repository in my Sonar account.
I had created a manual project per each maven module in my repository. I want to create just one mono repo Sonar as my respository in Bitbucket is already a mono repo.
When I try to create a mono repo, I get this error:
{“type”: “error”, “error”: {“message”: “No workspace with identifier ‘{XXXXXXXX}’.”}}
It seems to be a bad binding between my Bitbucket account and the Sonar organization but there is no way to unbind-rebind my organization.
How can I fix this? Is it only an action that can be done by the technical support?
You had filed this in the category for self-managed; that’s why I had to ask. I’ve recategorized this thread & I’ll flag it for the team. Can you share your org ID?
Could you please try uninstalling the SonarQube Cloud app from your Bitbucket Workspace settings, and then go back to your organization on SonarQube Cloud to attempt rebinding? You can find detailed instructions on changing your organization binding here.
If you still run into that workspace identifier error after trying this, please let us know. Since we already have your Organization ID, we can dive right in and investigate further on our end if the rebinding doesn’t do the trick.
I’ve removed the Sonar app from the list of Installed apps of my Bitbuket Worskpace. But then, my Organization binding in Sonar is still in Bound status. And my projects are not bound to a repository. I still have the same error while trying to search a repository to bind to a project.
The redirection button in my Organization bindings redirects to the “Alexandre_Huet” workspace, which doesn’t exist; my Workspace is “dwwzn”.
Do you still have access to the BitBucket Workspace named Alexandre_Huet? If you do, and can find the Sonar BitBucket application over there and delete it, it should clear the organization binding.
Alternatively, would recreating the organization be an option? That way you could ensure the organization binding is set properly to dwwzn.
The workspace Alexandre_Huetdoesn’t exist, or if it exists, I don’t have access to it.
Re-creating an Organization could be a solution, but it will be a lot of work on our side, so I would rather avoid this solution for a simple bad binding if there is another one.
Don’t you have a means to unbind it on your side directly?
Do you have any news about this issue? Is there any other way to fix this on your side than having us to recreate a full organization and re-configuring manuially everything?