Detecting old Code as New Code for past 1 year

SonarQube Cloud
,
1
  • ALM used Azure DevOps
  • CI system used Azure DevOps + GIT
  • Scanner command used when applicable (private details masked)
  • Languages of the repository: C#

Since the latest update of the Azure Plugin version 1.36.0 that happened on 24th January, all our projects are not doing diff correctly and detecting old code as new code for the past 1 year.

image
image833×435 20.3 KB

We have not changed any configuration and no lines of codes where changed.

Below is a sample screenshot

image
image1121×753 59.7 KB

Below is the build template used in azure devops to run sonar cloud.
sonarcloud-azure-template.txt (3.4 KB)

There two more points which we are not sure if they are related:

There is a warning about SCM provider auto detection.
image

Our Azure Access Token had expired and since then we renewed it and corrected the issue.

2

Hey there.

The New Code Period can be defined in your project settings, and you should check to make sure that something hasn’t changed there. An update of the extension should have no impact on your New Code Period.

This is strange, especially if you’re using Git on Azure DevOps. In some contexts this can affect the detection of new lines. Could something be impacting the existence of a .git directory when the analysis is executing?