:puzzle_piece: Problem Summary In our Azure DevOps + SonarQube setup, SonarQube is not reporting any New Code or issues during pull request (PR) analysis. This causes all PRs to show: :white_check_mark: “Quality Gate Passed” (due to 0 new lines/issues) :chart_decreasing: “0 New Lines” in PR analys…

Hi, As I believe you suspect, this is your problem: [image] user: Missing blame information for xxx files [image] user: Using fetchDepth: 0 and explicitly fetching the PR target branch Ensuring correct sonar.pullrequest.* parameters are passed Excellent. Now make sure the prerequisi…

Hi I see all the prerequisites as per the link are in place. Still I am not seeing PR decorated. I also see the PR analysis on sonarqube dashboard having 0 issues, there should be many for this test PR. [image] is there something specific i should verify?

Hi, Decoration is a different issue that “New Code always 0”. Let’s stick to that. First, what shows up on the Measures tab? Second, can you share you analysis log? Share the Scanner for .NET verbose logs Add /d:"sonar.verbose=true" to the… SonarScanner.MSBuild.exe or dotnet sonarscanner begin …

[sonarQube-measures] SonarQubeAnalyzeLog.txt (475.7 KB) I am using devops pipelines. Task is SonarQubeAnalyze@7

Hi, Thanks for the screenshot. I’d be curious what shows up in the Size portion further down on the left. Thanks also for the log. I’ve excerpted some interesting lines below: 2025-05-06T16:26:31.7149250Z 16:26:31.714 INFO: Found manual configuration of branch/PR analysis. Skipping automatic con…

to add some background. I had createdtestSonarqube-2 from recent release (5.23) and created PR to merge to main, which was on older release (5.22). This PR should have issues showing on sonarqube dashboard and PR being decorated. After I created this thread here, I noticed that main got updated with…

Hi, [image] user: I had updated my pipeline task to be: … sonar.scm.exclusions.disabled=true I guess that was since you ran the analysis, the log of which you provided above? Regarding this, I’m a bit confused: [image] user: after 5.23 merged into main, i see bunch of issues showing …

that’s another confusion I also have. the last merge to main happened on February 14,2025. Still it shows New Code: Since November 19, 2024. My new code setup is: [image]

Hi, This means that you haven’t changed your sonar.projectVersion string since November. HTH, Ann

No. we didn’t update sonar.projectVersion for any project. shouldn’t that mean that PR should show more issues than our expectations?

New Code always 0 for PRs – Issues detected only after PR is merged in Azure DevOps

SonarQube Server / Community Build

ganncamp (G Ann Campbell) May 1, 2025, 1:06pm 2

Hi,

As I believe you suspect, this is your problem:

Excellent. Now make sure the prerequisites are in place. Given that you’ve already ticked the fetchDepth box, I suspect that’s the problem.

HTH,
Ann

Topic		Replies	Views
Feature Branch Showing Bugs, Vulnerability and code smells in my PR that I haven’t touched SonarQube Server / Community Build sonarqube , scanner , azuredevops	21	1677	June 21, 2022
SQ adding comments for all code, not just changed code SonarQube Cloud	35	227	August 25, 2025
Sonarqube New Code Analysis is always empty SonarQube Server / Community Build sonarqube	14	3345	March 10, 2022
Sonarqube pull request analysis not showing any measures SonarQube Server / Community Build pull-request , sonarqube-team	7	3212	December 20, 2022
Block Pull request based on Quality gate code coverage on new code SonarQube Server / Community Build coverage , quality-gate , new-code	17	2741	September 6, 2022

New Code always 0 for PRs – Issues detected only after PR is merged in Azure DevOps

Related topics