PR Analysis/Decoration for Github Enterprise is not working

SonarQube
,
1

PR Analysis/Decoration for Github Enterprise is not working.

  • which versions are you using?
    • SonarQube - 7.8 and 7.9
  • what are you trying to achieve?
    • When a pull request is created, automated pull request analysis should be performed on the pull
      request by Sonarqube app.
  • what have you tried so far to achieve this?
    • Followed every step from the link https://docs.sonarqube.org/latest/analysis/pull-request/ multiple
      times with two different sonarqube versions, but nothing is working.
    • After following the steps to create the app, when i create the Pull Request, the PR is just getting
      created without actually performing any analysis.

We used Code Climate before and they really documented the steps very well that exactly says how to do and what to do at each step. Ref: https://docs.codeclimate.com/docs/github-pull-requests

2

Hi,

We are seeing the same issue with SonarQube 7.9.1 (but we were seeing it intermittently on 7.7, we did the upgrade thinking it was an issue in 7.7).

Link to our issue en case further details required: -

3

Hi,

Initially i installed 7.8.x.x and PR decoration didn’t worked on it, so i thought might be a bug in 7.8, so i installed latest version 7.9.x.x and still facing the same issue.

How it worked in 7.7 for you?
When you created a pull request, did the analysis happened with app itself OR did it trigger a jenkins job to perform the analysis and then results showed in github PR?

Please let me know.

4

Ours worked intermittently with 7.7.

We had a Jenkins job run the analysis on PR creation. Then SonarQube decorated the PR with the check (not the old comment way).

5

Karl,

Quick question.
How did you configure your pipeline to trigger jenkins build with PR creation and to pull the PR request number automatically . (i tried github pull request plugin but didn’t worked for me - https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin)

Really appreciate if you can help me this.

RK

6

We are using several plugins to do this.
GitHub Organisation Folder Plugin (this auto creates our jobs) - https://wiki.jenkins.io/display/JENKINS/GitHub+Organization+Folder+Plugin
SonarQube Plugin - https://plugins.jenkins.io/sonar

Make sure you set up your organisation to push Pull Request creation web hooks to Jenkins. The Folder Plugin then does all the magic

Then we have a shared library function that uses the env variable from GItHub Organsiation Folder and the pom.xml file to dynamically get all values for the sonar.properties file.

1 Like
7

Awesome, thanks for the quick response. i will try this today.

8

If you get issues let me know and I may be able to iron out your issues :grinning:. Obviously as ours isn’t working at the moment I am not confident in our answers yet.

9

Thanks for the assistance. Will give it a try and will let you know.

10

If you do get issues try increasing the log level to Debug or Trace on SonarQube. It seems some GitHub errors are only written in Trace (in the ce.log)

Try this page for more details on increasing log level
https://docs.sonarqube.org/latest/instance-administration/system-info/