Sonar Gerrit Plugin 2.3

Have you read this article?
https://stackoverflow.com/questions/48707380/sonar-gerrit-plugin-not-reporting-results/48770604#48770604

make sure that sonar qube report contains issues for the files changed in the commit that is being checked

if that's not the thing, make sure that you specified subproject paths (or just tick on auto-match option, it should make the magic if it is the case)

If all the above doesn't help, feel free to send me your sonarqube report (email can be found on the plugin page and in git repo). But I can't promise that I would be able to take a look anytime soon...

can you c/p valid sonarqube report or excerpt from report? I would like to compare if there is possible wrong layout of file Sonarqube generates from my side...

this is what I get from Jenkins log, so it is obvious that issues are somehow wrongly interpreted;
11:34:32 Report has loaded and contains 13570 issues*11:34:34* Issues to be commented: 0*11:34:34* Issues to be involved in score calculation: 0
 

I don't think it's layout. I think it's more about gerrit and matching your file names. Just check that your files that are included to the commit contain issues and try "auto-match" option.
If it were a report format problem, it wouldn't get parsed and you wouldn't see the message about 13570 issues (I don't think that someone can manage to create so many issues in one commit)

But if you want to see an example, look into test section of the plugin, here is an example: https://github.com/jenkinsci/sonar-gerrit-plugin/blob/master/src/test/resources/example.json

I can't find where to set "auto-match" option. Is it in job configuration?

Zlatko Mozanic see https://plugins.jenkins.io/sonar-gerrit Project Settings section