Integrate SonarQube with GitHub

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension) - SonarQube Server-2025.3-Enterprise Edition
  • how is SonarQube deployed: zip, Docker, Helm - ZIP
  • what are you trying to achieve - Integrate SonarQube with GitHub
  • what have you tried so far to achieve this
    Was able to create a GitHub app and apply all configurations related to the integrations. Able to import repositories into SonarQube as well. But failing in the Build stage.

During the build, seeing the errors during the SonarQube stage.

SONAR_HOST_URL=***
Warning:  
Warning:  Some problems were encountered while building the effective settings
Warning:  'profiles.profile[github].repositories.repository.id' must be unique but found duplicate repository with id github @ /home/runner/.m2/settings.xml
Warning:  
[INFO] Scanning for projects...
Warning:  1 problem was encountered while building the effective model for org.javassist:javassist:jar:3.18.1-GA during dependency collection step for plugin (use -X to see details)
[INFO] Starting Maven Build for BW6 Project.................................
[INFO] Checking for In-Project JAR dependencies if any and Pushing them to Local Maven Repository
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO] 
[INFO] XYZ.app.parent                          [pom]
[INFO] XYZ                                [bwmodule]
[INFO] XYZ.app                               [bwear]
[INFO] 
[INFO] --< com.abccompany.XYZ.application:XYZ.app.parent >--
[INFO] Building XYZ.app.parent 1.0.60          [1/3]
[INFO]   from pom.xml
[INFO] --------------------------------[ pom ]---------------------------------
[INFO] 
[INFO] --- sonar:5.5.0.6356:sonar (default-cli) @ XYZ.app.parent ---
[INFO] Java 17.0.18 Eclipse Adoptium (64-bit)
[INFO] Linux 6.11.0-1018-azure (amd64)
**Error:  Failed to query server version: Call to URL [***/api/v2/analysis/version] failed: servername.company.com: Name or service not known**
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for XYZ.app.parent 1.0.60:
[INFO] 
[INFO] XYZ.app.parent .......... FAILURE [ 15.108 s]
[INFO] XYZ ..................... SKIPPED
[INFO] XYZ.app ................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  19.168 s
[INFO] Finished at: 2026-02-10T19:17:37Z
[INFO] ------------------------------------------------------------------------
Error:  **Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:5.5.0.6356:sonar (default-cli) on project XYZ.app.parent: The scanner bootstrapping has failed! See the logs for more details. -> [Help 1]**
Error:  
Error:  To see the full stack trace of the errors, re-run Maven with the -e switch.
Error:  Re-run Maven using the -X switch to enable full debug logging.
Error:  
Error:  For more information about the errors and possible solutions, please read the following articles:
Error:  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Error: Process completed with exit code 1.

In the logs I see the server is not reachable.
Please let me know if I’m missing anything in the configurations/security configurations.

Sonar Community Roundup; March 7 - 13
2

Hi,

Based on your redaction, it looks like analysis called the correct URL, right? Which means that it’s time to talk to your network folks. It looks like something isn’t letting the build agent traffic through to your SonarQube server.

 
HTH,
Ann

3

Hi Ann,
Yes, it called the correct URL.

Since we are calling from GitHub Hosted Runner, which is having access to Internet and also is not in our private network, should we expose our SonarQube to Internet?

Or any alternative solution? As the network and security team may not approve exposing the service to Internet.

Thankyou…!!

4

Hi,

Your build agent has to be able to talk to your SonarQube instance.

 
Ann