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.
Here’s the latest update I’ve seen on what’s holding up “those guys” (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
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.
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.
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
(to 7.2.1, as there has been a minor update since).
(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: