Sub-issue of #1135, cause 3 of 3.
Master Build fails at the SonarCloud step. It is invisible on pull requests, because that workflow only runs on master, which is why it survived alongside the other two causes.
Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:5.7.0.6970:sonar
Failed to query JRE metadata: GET https://api.sonarcloud.io/analysis/jres?os=linux&arch=x86_64
failed with HTTP 403 Forbidden. Please check the property sonar.token or the
environment variable SONAR_TOKEN.
Most recent occurrence: run 30534095895 (2026-07-30). Last green Master Build: 2025-12-10, run 20115022310.
A 403 on the token endpoint means the credential is absent, expired or revoked, rather than the analysis itself failing.
What is needed
Someone with access to the SonarCloud organisation has to refresh the SONAR_TOKEN repository secret. I cannot: it is a credential, not a code change, so unlike the other two sub-issues this one has no pull request attached to it.
If SonarCloud is no longer wanted, the alternative is to drop the step from master.yml — but that should be a deliberate decision rather than a way of silencing the error.
Sub-issue of #1135, cause 3 of 3.
Master Buildfails at the SonarCloud step. It is invisible on pull requests, because that workflow only runs onmaster, which is why it survived alongside the other two causes.Most recent occurrence: run
30534095895(2026-07-30). Last greenMaster Build: 2025-12-10, run20115022310.A 403 on the token endpoint means the credential is absent, expired or revoked, rather than the analysis itself failing.
What is needed
Someone with access to the SonarCloud organisation has to refresh the
SONAR_TOKENrepository secret. I cannot: it is a credential, not a code change, so unlike the other two sub-issues this one has no pull request attached to it.If SonarCloud is no longer wanted, the alternative is to drop the step from
master.yml— but that should be a deliberate decision rather than a way of silencing the error.