SonarQube v7.9.1 (local instance) Scanner v4.0.0.1744 Plugin SonarPython 1.14.1.3143 (python) OS: Windows 10 v1803 I am experimenting with the leak period and new code. I did a very simple test by uploading two analyses for a small python project, but SonarQube did not report any “New code” (it is…

I already explained how the leak period set to previous_version works, I’m not going to argue it. [image] mmatrosov: Each build has its own build number. My first thought was that I upload each analysis with the version in the form major.minor.patch.build. This means each new analysis will have…

Just checked, exactly the same behavior with sonarqube-8.1.0.31237 and sonar-scanner-4.2.0.1873-windows

Hi, If I understood correctly, that’s the expected behavior. Once you change the project’s version, you reset the “new code period”. Meaning that you have a new baseline and from there on what is changed will be considered as “new code”.

I’m sorry, but this does not make any sense to me. I explicitly specify the leak period as “previous_version”. What else could this mean? And of course I upload new analysis each time I bump the version, and only then. This should happen simultaneously in my CI system. Also, not how the screenshot s…

Sorry, I think my last reply wasn’t very clear. With the “new code period” (or “leak period” as it was called in the past) set to “last version”, all changes included in the first analysis of the new version should be included in the “new code”. I agree that the naming and some labels could be imp…

Hi, Duarte, With the “new code period” (or “leak period” as it was called in the past) set to “last version”, all changes included in the first analysis of the new version should be included in the “new code”. That’s not what happened to me. “The new version” was 1.14 for me. Which included quit…

Ah, finally, I was able to reproduce your example on my machine. Thanks a lot! Without specifying projectDate, SonarQube will assign the current date as the analysis date. So no line will be “new” since the modification dates of all lines in the code being analyzed are before the last analysis of…

New Lines is equal to zero, even though SCM seems to work

SonarQube Server / Community Build

mmatrosov (Mikhail Matrosov) January 29, 2020, 1:18pm 8

I tried again with leak_period set to 1. I uploaded versions 1.13, 1.14 and 1.15, with sonar.projectDate set to 1st, 2nd and 3rd of January. Again, activity tab shows what I want, while New Lines under Measures tab is zero:

Topic		Replies	Views
New Code period not being respected if there is no initial version SonarQube Server / Community Build sonarqube	6	3355	November 15, 2018
SonarQube new lines are not correct SonarQube Server / Community Build sonarqube , scanner	4	6316	June 23, 2020
My numbers don't add up SonarQube Server / Community Build sonarqube , msbuild , coverage	8	1102	April 14, 2020
Using new code "since previous version" instead of "since BASELINE" SonarQube Server / Community Build sonarqube	26	15531	August 6, 2020
No issues seen if "new code period" is set to "previous version" SonarQube Server / Community Build	6	1964	October 6, 2020

New Lines is equal to zero, even though SCM seems to work

Related topics