Changing sonar.tests or sonar.sources causes "You're not authorized to run analysis" error?

SonarQube Cloud
1

Hello,

We are using SonarCloud with Github, launching from GitHub actions.
I just made a change to the sonar.tests= and sonar.sources= properties, and now the analysis execution is claiming that the authorization is incorrect.

This appears to be an incorrect error message, as we had just successfully ran with the same key earlier.
I’ve seen other users claim that changing the sonar.tests/sonar.sources value gave them the same error.

How can I resolve this issue?

Link to the PR where I made the change: Meta: Don't allow overlap in sonar cube file classification by bgianfo · Pull Request #9699 · SerenityOS/ser

Link to the failing analysis run: Meta: Don't allow overlap in sonar cube file classification · SerenityOS/serenity@5945333 · GitHub


INFO: EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
INFO: Total time: 2:27:01.893s
ERROR: Error during SonarScanner execution
INFO: Final Memory: 159M/537M
ERROR: You're not authorized to run analysis. Please contact the project administrator.
INFO: ------------------------------------------------------------------------
2

Nevermind, I guess it was because the job ran from a PR?

When running as a scheduled job it succeeded.

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.