Sonar Client/Server Architecturefleeting
This is what I guessed.
- on a CI or the computer of a developer, sonar-scanner is run. It scans the code, gets the SCM annotations of the code (among other things the date of the last commit that brought each line) and sends the analyses and annotated code to the server1, associated with a sonar.projectVersion value. Hereafter, we call this analysis the current version. Its date is either the date of scan or whatever you put in the projectDate property.
- the server stores the in a stack. The order of the sent analyses impacts how sonar will behave, so don’t send a past analysis (with sonar.projectDate) and rather create a new project from scratch.
- the server finds a date after which it considers the code as being new,
- either using a number of days from the date of the current version,
- or using a fixed date
- or finding another analyses as base and using its date
- if using the new code as being from the previous version, it checks the most upper analysis of the stack whose projectVersion is different from the current version 2.
- if using the new code as being from a fixed version, it find from the top of the stack the last analysis with that version.
- the server now has an interval of time (two dates) that define the temporal interval of new code,
- in the current version analyses, sonar finds all the lines whose annotation are in this interval -> those become the new code.
Notes linking here
SonarQube relies on “blame” data from your SCM repository to understand which code is “new”. If no SCM data is available, then no code can be marked new and thus no metrics “on new code” can be calculated. If you notice, you also have no duplications, technical debt, bugs or vulnerabilities “on new code”.
Changing the version label does not mean that there is new code. SQ core is looking in the SCM LOG files if there is new/changed code:
version 1=TRT-TMN_0.1.0.54 => date/time 1 in SCM LOG file version 2=TRT-TMN_0.1.0.62 => date/time 2 in SCM LOG file ==> new / changed items in SCM LOG file between these two points in time