After upgrade to SQ 6.7.5 target/sonar/issues-report/issues-report-light.html is not produced


(Roger Larsson) #1

SonarQube 6.7.5

mvn sonar:sonar -Dsonar.analysis.mode=preview -Dsonar.issuesReport.html.enable=true

I do not think the first warning has anything to do with the issue, but I include it for completeness…

[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be resolved: Failure to find org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in https://XXX.artifactory/proj-athena-release was cached in the local repository, resolution will not be reattempted until the update interval of athena-releases has elapsed or updates are forced
[WARNING] The artifact org.hibernate:hibernate-validator:jar:6.0.7.Final has been relocated to org.hibernate.validator:hibernate-validator:jar:6.0.7.Final
[INFO] — sonar-maven-plugin: (default-cli) @ athena —
[INFO] User cache: /home/rogerl/.sonar/cache
[INFO] SonarQube version: 6.7.5
[INFO] Default locale: “sv_SE”, source code encoding: “UTF-8”
[INFO] Issues mode
[WARNING] The use of the issues mode (sonar.analysis.mode=issues) is deprecated. This mode will be dropped in the future.
[INFO] Load global settings
[INFO] Load global settings (done) | time=354ms

Why does it list ‘issues’ when ‘preview’ is specified?
Why is not issues-report-light.html produced (did analyze that for build breaking)?

We are using gerrit, maven…, does even github PA mode work in this setting?

(Julien Lancelot) #2


Issues report was a deprecated feature and it has been removed in 6.6 by

You should have a look at SonarLint, which is producing far more interesting feature compared to issues report !


(Roger Larsson) #3

Documentation says it is Deprecated from 6.6 not Decapitated (Removed) - is it actually removed?

We are already using SonarLint but it does not enforce compliance…

(Julien Lancelot) #4

AFAIK this feature is for sure no more a core feature, so it’s either available with a plugin or it doesn’t exist anymore.

What is missing in SonarLint ?

(Roger Larsson) #5

Scripting, analysis needs to be run and rejected if failing gate before commit is merged.

Saw some stuff that Pull Request analysis from Developers Edition could help, but as we use gerrit and not github it is not certain that integration work - want the result to show up in gerrit not in another tool.

(Christophe Lévis) #7

From what I understand, the concept of change/review in Gerrit seems close to the concept of Pull Request.

With the developer edition, there’s also the concept of short-lived branch for the systems which don’t support Pull Request.
I think you should be able to analyze a change as a short-lived branch in SonarQube, and let Gerrit know the status that results from the analysis. The thread there and more specifically the 2nd answer can give you some hints about it.

(G Ann Campbell) #8

A post was split to a new topic: Analysis of related files in SonarLint

(Roger Larsson) #9

Reread your message again

“AFAIK this feature is for sure no more a core feature, so it’s either available with a plugin or it doesn’t exist anymore.”

Is there such a plugin?