We use CI integration from Azure DevOps to SonarCloud, with MSBuild Project. Mainly analysing C# and JavaScript files. Our problem is we have many thousands of long standing legacy code smells and other Sonar Cloud issues and this creates a huge number of Sonar Comments in any touched file in our P…

Further to my last message I can confirm that having run a complete scan on master with full depth git clone, and then a PR with a similar full depth git clone, the Sonar analysis is now correctly reporting only the changed lines of code and correctly attributing them to the PR owner. Many thanks f…

Hey there. Thanks for the report. Have you run an analysis of the main branch yet in SonarCloud (the branch this PR is being merged into)?

hi Colin - yes we have the main branch run every night. This shows all the 25K ‘legacy’ issues which we would like to be able to turn off in such a way that they do not get reported into the PR comments - there we only want to see comments relating to changes made by the PR author. We do not mind i…

[image] Marcus Richards: We do not mind if the issues are still visible in SonarCloud for the PR. The main problem is the proliferation of Comments in the PR. We do mind, as we really think that pull requests should only focus on changed code. Do you see any WARN messages in your analysis lo…

Well I do agree (I have signed up for the Clean Code Webinar!) … I have worked quite hard to make sure all the warnings are cleared, so using latest Node/npm and we have the full git clone, so no warnings about Shallow clone. We can see the full change history in Sonar which shows the originator o…

Something is funny here. I’ll flag this for an internal team to investigate. In the meantime, it would be great if you could prepare DEBUG analysis logs of a PR that behaves like this (the sonar.verbose=true analysis parameter should do the trick). Whoever takes a look at this thread can open a priv…

I think I may be on to something … the nightly run on master was not correctly pulling the full git repo for master (for disk space reasons we had limited it) so the change history was not fully annotated (blame). I have now managed to get a full run on master and rerun the PR and I think it is now …

Thanks a lot for the follow-up! Does that mean you have different pipelines set up for master compared to your PRs (with a different checkout strategy)? Just want to make sure I understand fully to help the next person who has the same issue. :slight_smile:

It was a bit tricky to fix because the fixes I was making were in the YAML for the PR, so although I could run the Sonar pipeline in the PR, I could not run it in master as that would not have my changes yet (catch 22!)… so the master run was not correctly pulling the complete git version history. S…

Can we hide legacy issues in Azure DevOps PR annotations so we only see comments for changed code?

SonarQube Cloud

Topic		Replies	Views
Extra Issues highlighted on lines with no code change SonarQube Cloud sonarqube-cloud	21	623	July 1, 2024
Problem with detecting changes on PRs in Azure DevOps SonarQube Cloud csharp , dotnet , azuredevops , sonarqube-cloud	3	509	June 1, 2023
Why add comments for lines of code that don't change? SonarQube Cloud scanner , pull-request , azuredevops , sonarqube-cloud	5	598	November 17, 2023
PR check the whole file and not just changed code in Azure DevOps SonarQube Cloud azuredevops-services , pull-request	7	1919	October 3, 2023
Azure Devops SonarCloud - PR Annotations Not Working As Expected SonarQube Cloud coverage , dotnet , azuredevops	4	1346	May 13, 2022

Can we hide legacy issues in Azure DevOps PR annotations so we only see comments for changed code?

Related topics