All geek questions in one place

Analysis Modes in SonarQube 5.2

I'm currently trying to understand the analysis mode changes in SonarQube 5.2. Changing the full mode to publish is simple enough, but removing the incremental mode and adding the issues mode that really throws me.

It was previously assumed that incremental mode can be used to view problems only in files that have been changed, while the preview mode will analyze the entire project. Does this still have a problem mode?

My project is huge (1-3 hours for analysis from scratch), so the ability to simply analyze gradually for things like pre-commit checks or Github integration is pretty much required for the tool to be used by our developers.

Any clarification that people can provide will be appreciated.

+5
source share
1 answer

We decided to rename the preview mode to issues mode, as this is more understandable: all this concerns problems (there is no calculation of duplication, coverage, differential measurements, ...).

The presence of a real preview mode (that is, a real public analysis without fixing the results at the end), which will allow checking the quality of the gate, is planned for 5.4: https://jira.sonarsource.com/browse/SONAR-6763

We also removed the incremental mode, which was very poorly named. In fact, it was a “just” partial analysis. You can (almost) achieve the same result by filtering the input files with sonar.inclusions. But we know that for pre commit analysis it may be interesting to automatically optimize issues analysis only using sensors for modified files. That's why we will present something similar (but not quite the same) in 5.3, which should be released by the end of December: https://jira.sonarsource.com/browse/SONAR-6931

+6
source

Source: https://habr.com/ru/post/1235060/

More articles:


All Articles