SonarQube does not find all issues

The version of SonarQube: 6.7 (build 33306)

I have a java file that is being analyzed (there are some issues found in that file in SonarQube), but one issue is not being reported. On the other hand, SonarLint does report the issue. I have SonarLint bound with the SonarQube project (so I’m using the same quality profile and SonarQube found this issue in some other class, so it’s not the case that it has this rule disabled).

I’m attaching screen-shots from both SonarQube and SonarLint. I don’t know why SonarLint shows it found the issue 2 hours ago… there has not been a change in the file for 5 months and on the specific line for 8 months.

Why does SonarQube not report the issue?

Thanks,
Pedro

SonarLint:

SonarQube:

Hi,

SonarQube 6.7 is long past EOL. You should upgrade immediately. Your upgrade path is:

6.7 -> 7.9.4 -> 8.5 (this step optional)

I suspect that even though your rule sets are the same via connected mode, the rule implementations may not be & thus a “smarter” version of the rule in question is being run in SonarLint that in SonarQube.

 
Ann

Thanks Ann for the info, hopefully I will managed with our DevOps team to upgrade. :slight_smile: