Pull request - Quality gate new code not being scanned


We’re using:

  • SonarQube Developer Edition 8.9.7
  • Github
  • Google cloud platform
  • Maven
  • Java 1.8

Issue in short: when we update a pull request and create an issue, this issue is not reported by SonarQube on the pull request.


  • we create a branch from the master
  • we create a pull request from this branch to the master
  • we introduce, for test purpose, a high severity issue

The new code is not visible in the code tab

The arguments passed
mvn sonar:sonar -P sonarscanner -Dsonar.analysis.buildNumber=$BUILD_ID -Dsonar.analysis.commitSha=$COMMIT_SHA -Dsonar.qualitygate.wait=true -Dsonar.pullrequest.branch=$BRANCH_NAME -Dsonar.pullrequest.base=master -Dsonar.pullrequest.key=$_PR_NUMBER -Dsonar.projectKey=com.snapengage:snapengage -Dsonar.organization=default-organization -Dsonar.language=java -Dsonar.binaries=build/classes -Dsonar.scm.revision=$(git rev-parse --abbrev-ref HEAD) -Dsonar.verbose=true -X;

In the logs, it shows “SCM reported 0 files changed in the branch” and the Merge base hash is pointing to the commit of the Pull request branch.

I added Dsonar.scm.revision=$(git rev-parse --abbrev-ref HEAD) after checking a similar issue here but that hasn’t worked.

Please let us know what needs to be changed in order to get this working.

Best regards,

Hi Akshay,

Welcome to the community!

Could you provide your full analysis log (text, not screenshot) starting from the analysis command?


Hi Ann,

The logs contain sensitive information, I would prefer if I can share the full analysis log privately. Can you provide an email ID to which I can send the logs?


Hi Akshay,

Feel free to redact the sensitive information.