Must-share information: SonarQube Server Enterprise Edition v2025.4.2 and Visual studio IDE Version: 9.1.0.15828. Make numbers for new code on main branch correct. setting sonar.projectVersion to $(Build.SourceVersion) (git hash) We have projects that follow the git workflow with short lived bran…

Hi I have tried to remove the projectVersion when a branch is being build, but this still does not work. It looks like if I do not set sonar.projectVersion it just defaults to 1.0. I did a test where the GIT updates look like this. [image] The Merged commits are on the main branch and the thre…

Hi, Yes, you must have a sonar.projectVersion value. If you don’t provide one, it will default. Since you’ve set the main new code definition to ‘previous version’ then other branches have nothing to do with what’s showing up in main. Beyond that, I’m not able to follow what you’re doing and what …

Hi In the example above there are only 2 builds (SonarQube analyses) on main. In the first analysis the version number is 87c8940f33… and in the second one it is 46186be548… So it was changed. There are 3 commits between the two builds. Added new code Second new line New member The first commi…

Hi, And what were the sonar.projectVersion values for these 3 runs? Ann

Hi If with runs you mean SonarQube analysis then there are only 2 runs on the main branch. There is one that was done november last year. In this one sonar.projectVersion was set to 87c8940f33efc92f96d9055109191148ef0dcb18. This is also the GIT hash of the “merge commit” that the analysis was done…

Hi I have attached the output from DevOps when the “Run Code Analysis” task was preformed in the build yesterday. Run Code Analysis.txt (30.5 KB) I cleared some information that might be a bit sensitive with stars. The analysis was not executed with “sonar.verbose=true”. /Kennet

Hi Kennet, Can you give me a verbose log, please? Thx, Ann

Hi I did a re-run of the last build with verbose. So this is a build with version 46186be5482f06ef0550769106b2283f799d2d4b again. The “Added new code” commit is still not shown as “new code” in SonarQube. Run Code Analysis verbose.txt (215.6 KB) /Kennet

Hi Kennet, Thanks for the log. I don’t see anything unusual about the SCM data (altho “493 files ignored because of scm ignore settings” does seem like a lot.) The log also confirms your revision id of 46186be5482f06ef0550769106b2283f799d2d4b. So, when you look in Git, what are the changes betwee…

All New code not detected when using Previous version

SonarQube Server / Community Build

ganncamp (G Ann Campbell) March 19, 2026, 3:29pm 10

Hi Kennet,

Can you share your analysis log?

The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.

This guide will help you find them.

Ann

Topic		Replies	Views
0 New Lines to cover and to analyze for duplications on the main branch SonarQube Server / Community Build	12	1481	September 13, 2021
Confusion about New Code Defintion with 'Previous Version' and Branches SonarQube Server / Community Build branches , new_code	10	5346	April 29, 2022
New code period is behind last project version SonarQube Server / Community Build	3	126	February 20, 2025
New Code determination based on "Previous Version" - how to recompute? SonarQube Server / Community Build	7	641	May 26, 2022
New Code Definition is working wrong SonarQube Server / Community Build sonarqube , new_code	4	2694	August 31, 2022

All New code not detected when using Previous version

Related topics