Gitlab Merge Request decoration (self-hosted) with SonarCloud

[warden (Radek Antoniuk)]

Context:

• SonarCloud, organisation on OSS plan
• Gitlab Ultimate self-hosted (18.8)
• Neither Organisation nor project are bound - because this is not supported with Gitlab self-hosted apparently

Question:

• What is supported in this scenario in the context of Gitlab Merge Request decoration?

According to the docs, Inline comments are not supported, but the overview status should be added in the MR by SC.

This doesn’t seem to work for us:

• the MR is scanned successfully and is visible in SC
• but the Overview is not added on Gitlab side

Some other threads suggest that organisation/project binding is required, but the docs do not reflect that (and they are quite old already).

SonarCloud + GitLab =

This feature is now live on SonarCloud! Documentation is available at the bottom of the Analyze your repository with GitLab CI doc page on SonarCloud. We’re now working on pushing results in the Merge Requests UI, this should come in a week or two.

Gitlab.com merge request decoration

@gbrissonnette Can you go to [your project] > Administration > Background Tasks and give us a screenshot or give us some of the IDs of the tasks listed there?

Anything that should be visible in (which) logs about this?

[warden (Radek Antoniuk)]

Just found this:

Troubleshooting Missing Pull Request Decoration in SonarQube Cloud

It’s a frustrating scenario: your pipeline runs, SonarQube Cloud completes its analysis, and the quality gate is green—but the results never appear on your pull request. You’ve followed all the steps, so what’s going wrong? This guide will walk you through the most frequent causes of this issue and how to resolve them. The #1 Cause: Incorrect Organization / Repository Binding More often than not, the problem lies in an incorrect or invalid configuration linking SonarQube Cloud to your DevOp…

and that again mentions org binding. Further down I see also:

Ensure that the Gitlab token provided to SonarQube Cloud has the api scope

but right now we are not even passing any Gitlab token, because it cannot be configured anywhere. The Pull Request section in Settings doesn’t even show Gitlab:

[ganncamp (G Ann Campbell)]

Hi,

Yes, this is about binding, which is what tells SonarQube Cloud (among other things) where to go when it’s time to decorate a PR/MR.

Without that, I’m afraid there’s not much to be done, altho I will route this to the docs team.

 
Ann

[warden (Radek Antoniuk)]

Can I monitor a roadmap / feature request somewhere to see if Org/Project binding is planned to be supported with self-hosted?
This feels like a major missing feature for self-hosted instances..

[ganncamp (G Ann Campbell)]

Hi,

I’ve flagged this for the documentation team to address the things you noted aren’t there. After that, I plan to pass it off to the PMs. I doubt there’s already a public portal card tracking this, but let’s see what they come up with.

 
Ann