Any update or is this anything I should focus on in the debug logs?
Hello @jeverett ,
Could you please share with us the project scanner properties
from the background task on the project where the Merge Requests are failing?
Still in the background task, is the analysis considered a Pull Request
analysis or a Branch
analysis?
Also, are you using GitLab CI?
Hi,
We are experiencing a similar problem. For some projects, sonarqube is sending comment on merge requests, but for some projects there is no post request in the debug logs.
I am wondering if any of you found the root cause which can point me in the correct direction.
We are using Gitlab CI.
Question: is there any configuration in the sonar scanner analysis which might affect this or is it only a configuration on sonarqube server?
Hi again,
I have seen that there was a change on this with versiob 8.1. Here is the information about it: [SONAR-17711] - Jira
Our sonarquber version is 9.3. If i did not misunderstand for this version, this configuration should be done on server side. But I could not find documentation with version 8.1 where this configuration came into picture. So my questions:
- why donât you have documentations for all versions?
- what configuration should I do on server side for merge request decoration on server side and how to do it?
Hi again,
I have found our problem and wanted to share here. In the merge request job, I had âsonar.branch.nameâ parameter and it causes Sonarqube does branch analysis only (if I am not wrong). So it was not sending any merge request comment to Gitlab.
After removing this parameter from script, it was able to send the comment on Gitlab.
I hope this helps others.