Menu
Which are the key differences between these preview and issues modes of SonarQube (greater than 5.2) analysis?
Considering http://docs.sonarqube.org/display/SONAR/Concepts the main differences between publish and preview is that preview reports only issues (no measures) and no report is pushed back to the SonarQube server; this idea is clear. But what about issues? It is written that issues is the same as preview, but should be used only for tools development. I'm a little confused, what do they mean by tools?
920
What happens during analysis? During analysis, data is requested from the server, the files provided to the analysis are analyzed, and the resulting data is sent back to the server at the end in the form of a report, which is then analyzed asynchronously server-side.
The theory is that preview mode is what a end user should use for example when using issues report feature. The goal is to run an analysis without publishing results. The issues mode is a technical mode similar to preview but focusing only on issues. It can be used in combination with one of the pull request analysis plugin (like GitHub plugin).
Now in practice, in SonarQube 5.6, they are doing exactly the same thing. It is a bit confusing I admit, so maybe we could try to simplify this.
143
sonar.analysis.mode Deprecated since SQ 6.6. see https://docs.sonarqube.org/latest/analysis/analysis-parameters/
28
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
