Must-share information (formatted with Markdown ): which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension) SonarQube Version 8.9 (build 43852) Azure DevOps Server 2020 Update 1.1 (on premise) Version control: TFVC what are you trying to achieve We have “Main” br…

Hi Christian, My understanding is that using Reference Branch means the differences between the branches are what’s considered New Code and the version number isn’t considered relevant. Note that in 9.3 we did some work on the reference branch logic ( SONAR-15697 , SONAR-14929 ). I can’t guarantee it…

Hi again, Also, this may be relevant: [image] Compute New Code for branches using master as reference on tfvc SonarQube Hello @tiocalibe welcome to the SonarSource community! If I understand your report, the Reference Branch new code period is not working for projects h…

Hi Ann, thank you for your feedback! It seems the sonar-scm-tfvc plugin does not support this implementation currently. We need to discuss how we want to proceed. Another question about “Previous version” setting. Is this working with TFVC? Can you explain how this works under the covers please? …

Hi Christian, I believe TFVC works in general for new code detection and ought to be okay with a previous_version setting. Regarding the 'wrong" new issues you’re seeing, we should dig into those cases individually. For one or two issues can you provide the rule that raised the issue the last-m…

Maybe things got mixed up because I have also run an analysis on the feature branch before I had run the analysis on the main branch after the merge of the feature branch. So before I come back to you with detailed issues analysis I will first delete and clean up all analysis results we had so far …

I have deleted the feature branch from Sonarqube and I tried to calculate new code issues, measures etc. just with the main branch and the previous version setting. Now it shows a few less errors but still there are issues, security hotspots detected in the new code tab. The affected files have been…

Hi Christian, No, this doesn’t feel like a lot to work with. Can you also show the blame date on those issue lines? And when your New Code Period started? Ann

Hi Ann, I was busy in the project with other stuff, sorry. In the meantime I have completely deleted the project in Sonarqube to have a fresh starting point and I have created a new project with new name and key. I did again two analysis, one on the main branch before the merge of feature branch, a…

Hi, [image] CFA: Note, actually I just merged into a TFVC shelveset and run the build with that shelveset without checking into main It’s possible that this is the problem. To be honest, I don’t know what a TFVC shelveset is, but new code detection relies on SCM data so if you’re doing somet…

As you proposed we use now the lg2de / sonar-scm-tfvc plugin. Now the new code calculatoin works much better! Thank you Ann for your time and support!

Confusion about New Code Defintion with 'Previous Version' and Branches

SonarQube Server / Community Build

ganncamp (G Ann Campbell) February 25, 2022, 7:17pm 3

Hi again,

Also, this may be relevant:

Ann

Topic		Replies	Views
All New code not detected when using Previous version SonarQube Server / Community Build sonarqube , coverage , new_code	24	277	August 13, 2026
New Code determination based on "Previous Version" - how to recompute? SonarQube Server / Community Build	7	641	May 26, 2022
New Code on reference branch fails when compared to previous version SonarQube Server / Community Build sonarqube	2	76	April 25, 2025
Making a decision about New Code SonarQube Server / Community Build new_code	4	447	March 1, 2024
New Code Definition is working wrong SonarQube Server / Community Build sonarqube , new_code	4	2694	August 31, 2022

Confusion about New Code Defintion with 'Previous Version' and Branches

Related topics