We just started getting 403 errors in pipeline pipe: ERROR Failed to query JRE metadata: GET https://api.sonarcloud.io/analysis/jres?os=linux&arch=x86_64 failed with HTTP 403. Please check the property sonar.token or the environment variable SONAR_TOKEN.
This was working a couple of hours ago. We did not make any changes to the pipeline, we are using sonarsource/sonarcloud-scan:4.1.0. I went to the project to generate a new token and updated the environment variable with the new value, same error. This is blocking everything, does anybody have any suggestions other that completely bypassing the scan?
Weirdly, when I reran the whole pipeline instead of just the failed step after a few minutes it started working again. Not sure if it made a difference, or the token takes a while to update, or they resolved the issue on their end and our new token has nothing to do with it…
Hi all! Thanks for bringing this issue to our attention. I can confirm that this was indeed an issue on SonarQube Cloud side. Our engineering team reacted quickly and rolled back the affected component, which is why you saw the API calls working again.
Hi @andres, thank you for confirming. Do you have any timestamps for impact start/resolved that you could share, so we can verify that the failures we saw yesterday were caused by this and not other internal issues? Thank you!