Sonarqube Github Pull Request Integration

github
pull-request
sonarqube

(Bernardo Vale) #1

Hey guys!

We’re trying to perform the pullrequest integration with Github enterprise as described in this document:

https://docs.sonarqube.org/display/SONAR/Pull+Request+Analysis

The only part that doesn’t work is PR decoration.

The doc says:

The first thing to configure is the authentication token that will be used by SonarQube to decorate the PRs. This can be configured in Administration > Pull Requests. The field to configure depends on the provider.
_ _
For GitHub Enterprise or GitHub.com, you need to configure the “Authentication token” field. For VSTS/TFS, it’s the “Personal access token”.

The problem is that there is no page Administration > Pull Requests.

We’re running Sonarqube version 7.1


(Colin Mueller) #2

Bernardo,

Pull request analysis became available in SonarQube 7.2. Time for an upgrade :slight_smile: (to 7.2.1, as there has been a minor update since).

Colin


(Bernardo Vale) #3

Good to know Colin :slight_smile:

I will as soon as you guys merge this PR: https://github.com/SonarSource/docker-sonarqube/pull/183

Thanks!


(Colin Mueller) #5

Benardo,

Here’s the latest update I’ve seen on what’s holding up “those guys” :wink: (SonarSourcers will have “SonarSourcer” or “Leader” indicated next to their name on this forum, and the SonarSource logo on their avatar) on the docker image: SonarQube 7.2 Released

Colin


(Bernardo Vale) #6

Thanks Colin!

This is the only thing blocking us from moving from Sonar 4 straight to Sonar 7.2 (we have a non prod 7.1 but we’ve decided to wait for 7.2) so you can imagine my anxiety.


(Colin Mueller) #7

Bernardo,

You mention “moving from Sonar 4 straight to Sonar 7.2”

Just checking – have you tested the full upgrade path with your test SonarQube environment, rather than just standing up a new sub-prod 7.1 instance? I’m asking since you’ll have quite a (probably uncommon) upgrade path if you’re currently on SonarQube 4 (4.5.7 -> 5.6.7 -> 6.7.4 -> 7.2.1).

Advancing through each LTS before landing on Latest is the supported upgrade path.

Colin


(Bernardo Vale) #8

Hey Colin, we’re not performing a upgrade. We will move projects from the old instance v4 to the new instance v7. We don’t really care about the history :slight_smile: