Sonarqube github decoration doesn't work


I follow the documentation regarding GitHub and Sonarqube decoration integration, sadly it doesn’t work.
I get from the PR analysis page in the server a warning in the upper right side:
“Pull request decoration did not happen. Please install SonarQube Github application on the repository’s organization or user.”

This is my enviroment and sonar configuration:

  • Sonarqube version: 7.7 DE
  • Sonar Sacnner: 3.3.0 Linux
  • Sonar scanner command from Jenkins where $prNum gives me the pr number only:

sonar-scanner -Dsonar.projectVersion=1.${BUILD_NUMBER} -Dsonar.pullrequest.key=$prNum -Dsonar.pullrequest.branch=${env.CHANGE_BRANCH} -Dsonar.pullrequest.base=${env.CHANGE_TARGET}

I also configured in the project the sonar.pullrequest.provider=GitHub and sonar.pullrequest.github.repository = MyOrg/MyRepo

In the server administration config, I added GitHub API URL:, GitHub App name, GitHub App ID, GitHub App private key.
I follow the instructions from [] to set GitHub app install it to the repo but under checks, it shows me it’s on Queued state.

We are using Github Enterprise.

Am I missing something? we also have for this repo Jenkins pr checks, is this can cause an issue?



Please check in the SonarQube logs (more specifically, in web.log) if you see one of these messages:

  • “Github App integration enabled”
    • The log message will contain details about the configuration. Verify they are correct.
  • “Github App configuration is invalid”

I hope this will help you resolve the issue, please let me know how it goes.

Note that in the latest release of SonarQube we have made some improvements to help diagnose such configuration issues. If you can upgrade, I recommend to do that and try again.

I am seeing a similar issue with our set up. My ticket is here:

Also someone else in the community seems to be having the same issue:

I spotted this so I thought I would post it.
Try changing the and increase the logging to Debug or even Trace. The GitHub calls are only written in debug when it errors.

Check this page on setting log levels -