Sonar considering previous commit files also for the current build commits

[venkat_one (venkat)]

Must-share information (formatted with Markdown):

• which versions are you using (SonarQube 8.6, Scanner 3.7, Plugin maven , and any relevant extension)
• what are you trying to achieve: Sonar should report issues/bugs on new code only.
• what have you tried so far to achieve this: I have commented few lines of code and pushed the code to gerrit and jenkins job triggered automatically. As part of build sonar considered previous build files and also reported issues on that files which is not part of my commit.

Could you please help me why sonar considering previous commit files?

Thanks
subbu

[Colin]

Greetings subbu,

Let me suggest you stick to a single topic describing these issues. I will close this one and leave this one open.

Sonar doing analysis on other files which is not related to current commit

Must-share information (formatted with Markdown): which versions are you using (SonarQube 8.6, Scanner 3.7, Plugin -maven sonar scanner , OS -linux ) what are you trying to achieve: Sonar should report/bugs on New code only what have you tried so far to achieve this: We have defined to consider New code as “previous version(default)” and we are passing sequence number for the -Dsonar.project.version, so that every build/analysis can be considered as “new code”.But Sonar is not reporting the …