Local scan and pipeline scan are inconsistent

SonarQube for IDE IntelliJ Platform
1

Please provide

  • Operating system: win11
  • SonarLint plugin version: 10.6.2
  • IntelliJ version: 2024.1.6
  • Programming language you’re coding in: java
  • Is connected mode used:
    • Connected to SonarCloud or SonarQube (and which version):SonarQube

And a thorough description of the problem / question:
Using the sonarlint plugin to connect to sonarqube and configure the correct project rules, the local scan results are inconsistent with the scan results using sonar-maven-plugin on git flow

2

Hey there.

Do you mind sharing a specific example?

3

image
image1563×25 2.16 KB

For example, this rule can be scanned by using sonarqube on the server using sonar-maven-plugin to scan out duplicate code blocks, but local sonarlint cannot scan them out. There are also some other rules that can be scanned locally but will not be reported on the server.

4

This is a rule that’s unavailable in SonarLint (all the rules in the common-<language> repository are) because they are computed server-side. It’s expected that these issues aren’t raised by SonarLint.

That being said, these rules have been deprecated for a while, and finally removed in SonarQube v10.0. That might be good enough reason to remove them from your Quality Profiles.

6

That is to say, sonarlint will not apply the expired rules on sonarqube, right? The sonarqube on the server is not maintained by me, its version is very old, and even the new version of sonarlint is no longer compatible, and I cannot modify these rules.

7

These rules could never been run in SonarLint (even when they were actively supported) because they were computed SonarQube server-side.

If parity between SonarLint and SonarQube is important, then using an up-to-date version of SonarQube and Connected Mode is going to be very important.