Project <-> mono-repo binding issues

SonarQube Cloud
1

Hi, we’re using sonarcloud together with a GitHub C# mono-repo. Our CI is running on GH-actions (we do use the sonarscanner dotnet tool together with a lot of API calls to configure the SonarCloud projects)

We have for each project the mono-repo config enabled for quite some time but didn’t had any repo binding active.
This all worked quite well but when a QG was failing we didn’t had a easy quick way to see if it’s was the QG or the tests itself who where failing. Shortly said, we lacked the PR decoration functionality

As our CI is fully managing the SonarCloud project through API calls, we want todo the same with the repo binding, while doing this all, we encountered some issues:

  • there are 2 ways of binding a repository and are threated differently by SonarCloud:
  • you cannot unbind a repo

While trying out the binding functionality, we have bound the above project through API and UI, but now we’re having issues with Sonarscanner, on that project the PR’s cannot be found any more

image
image1370×212 17.4 KB

As we see it, this feature is still in alpha phase (if not then the API docs can be heavily improved, if is, then we would like to reset our projects to unbounded completely)

this is the API endpoint we’re using todo the binding => SonarQube Cloud

kind regards

2

Hi,

The only way to unbind a repo is to delete the project(s) from SonarQube Cloud and start over. Which may be what you have to do.

The APIs aren’t necessarily built for your use. They’re what we needed to build to make the product work. And some of them we exposed publicly. But for this - and any time you’re having trouble - you should default back to UI usage.

 
HTH,
Ann

3

Hi,

This smells like an incomplete feature, or at least a feature that’s hacked in.
This also casts doubt on the quality of the SonarCloud product itself.

Public endpoints are … public endpoints. meaning they can be used by customers and passed the internal QA.

Kind regards