Hello we are using SonarQube™ Developer EditionVersion 9.8 (build 63668) with Azure Devops.
In my pipeline I use the following SonarQube Prepare:
Task : Prepare Analysis Configuration Version: 5.9.0
sonar.exclusions= **/TelerikWinform/*.*,**/bootstrap/**/*.*, **/Scripts/**/*.js,**/APropos.xml,**/*.generated.*,**/*.sql,**/*.SQL,**/*.Sql
sonar.pullrequest.key=$(System.PullRequest.PullRequestId)
sonar.pullrequest.branch=$(System.PullRequest.SourceBranch)
sonar.pullrequest.base=$(System.PullRequest.TargetBranch)
I do find the analysis in sonarqube with the right PR-ID marked as for merge into .
Nonetheless, the analysis trigger some Minor issues (but not all minors issues) that are already existing in the target branch. Some PR will also have false positive in other category as Critical or Major.
Strangely, I can affirme that the issues that are triggered are not inside files that has been modified by my PullRequest, which cause funny comment from Sonar on the pull request : “This file no longer exists in the latest pull request changes. It may have been moved or deleted.[View the comment in its original context.]”
To check the diff from the target branch, I used the git command: git diff --name-only origin/<the right branch> .
Is this a known issues ? Do I miss something in my config ?
Speaking of PR analysis, is there a way to known the issues from the target branch solved in a PR ? (bonus question)