Runtime-Environment
- Sonarqube Server Enterprise Edition v2026.1.2 (121356)
- Docker
- Maven-Plugin sonar-maven-plugin:5.6.0.6792
- Maven-Plugin connects to Sonarqube-Server via proxy-server
- Proxy-Data is definded in maven-settings.xml
We try to start an sonarqube analysis in maven-build-run with the newest sonar-maven-plugin (5.6.0.6792). Does not work.
Output:
[INFO]
[INFO] — sonar-maven-plugin:5.6.0.6792:sonar (default-cli) @ xxx—
[WARNING] Using an unspecified version instead of an explicit plugin version may introduce breaking analysis changes at an unwanted time. It is highly recommended to use an explicit version, e.g. ‘org.sonarsource.scanner.maven:sonar-maven-plugin:5.6.0.6792’.
[INFO] Java 11.0.14 Oracle Corporation (64-bit)
[INFO] Linux 5.15.0-200.131.27.el9uek.x86_64 (amd64)
[INFO] MAVEN_OPTS= -Xmx512m -Djava.io.tmpdir=<somedir>/.maven/tmp/
[ERROR] o.s.s.l.ScannerEngineBootstrapper - Failed to query server version: GET ``https://sonarqube.x.y/api/server/version`` failed with HTTP 400 Bad Request
If im changing the sonar-maven-plugin-version to the version before (5.5.0.6356) all works without an problem (no extra configuration changed, only going back on one release version of the plugin).
It seems that the newest version have a problem to get an connection to query the server version via proxy.
Output from previus version:
[INFO] --- sonar-maven-plugin:5.5.0.6356:sonar (default-cli) @ xxx ---
[INFO] Java 11.0.14 Oracle Corporation (64-bit)
[INFO] Linux 5.15.0-200.131.27.el9uek.x86_64 (amd64)
[INFO] MAVEN_OPTS= -Xmx512m -Djava.io.tmpdir=<somedir>/.maven/tmp/
[INFO] o.s.s.l.ScannerEngineBootstrapper - Communicating with SonarQube Server 2026.1.2.121356