The SonarQube Scanner plugin was included in the Jenkins plugin bill of materials bill of materials in 2024. That helps us detect compatibility issues through automated tests before those issues are discovered by users.

However, the plugin fails automated tests with Java 25. Jenkins has supported Java 25 since Jenkins 2.541.1 in January 2026. The Jenkins plugin BOM will be compiling and testing with Java 25 very soon. The test failures with the SonarQube Scanner plugin are a problem for that transition.

The plugin repository does not have a Jenkinsfile, so it is not tested as part of the ci.jenkins.io testing of plugins.

I'll temporarily block the SonarQube Scanner plugin tests in the Java 25 portion of the Jenkins plugin bill of materials as part of the Java 25 pull request. If prompt action is not taken to assure that the tests compile and run with Java 25, I'll propose that we remove the SonarQube Scanner plugin from the Jenkins plugin bill of materials.

Users are not directly affected when the plugin cannot be compiled and tested with Java 25, but Jenkins developers will not detect compatibility issues as effectively if the SonarQube Scanner plugin must be removed from the Jenkins plugin bill of materials because it does not compile and run tests with Java 25 successfully.