SonarCloud PR Analysis stopped working

SonarQube Cloud
,
1

Hi,
We have integrated SonarCloud with PR analysis on our project and it was working until last week. We have changed anything on our side of configuration and we noticed that this happened between this two builds on the SonarQube Cloud Server versions:

  • SonarQube Cloud: Server version: 8.0.0.60080 SUCCESSFUL
  • SonarQube Cloud: Server version: 8.0.0.60094 FAILED

We are using Integration with Azure DevOps Services. The PAT (personal access token) was refreshed, but without success.

Here are the log details:

Logs

`ant/sonar.xml:96: java.lang.IllegalStateException: Unable to load component class org.sonar.scanner.scan.filesystem.InputComponentStore
at org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer.getComponent(ComponentContainer.java:52)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
Caused by: java.lang.IllegalStateException: Unable to load component interface org.sonar.scanner.scan.branch.BranchConfiguration
at org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer.getComponent(ComponentContainer.java:52)
Caused by: Could not find the pullrequest with key ‘101586’
Caused by: com.sonarsource.scanner.engine.webapi.client.HttpException: Error 404 on https://sonarcloud.io/api/alm_integration/show_pullrequest?project=***&pullrequestKey=101586 : {“errors”:[{“msg”:“Unable to find the pullrequest with key 101586”}]}
at com.sonarsource.scanner.engine.webapi.client.BaseResponse.failIfNotSuccessful(BaseResponse.java:22)
at org.sonar.scanner.http.DefaultScannerWsClient.failIfUnauthorized(DefaultScannerWsClient.java:82)

`

Does anyone know why this happens? Is it a known issue and could it be fixed in a future release of SonarQube Cloud Server version?
Thank you.

2

Hey there.

I’m not sure which token you updated, but if the issue appears only in Pull/Merge Request pipelines, then most likely the token set in your global Administration > Organization Settings > Organization binding is no longer valid. This token is used to query information about the pull/merge request during analysis.

(and yes, it’s very annoying that the error message isn’t more clear about this :()

Can you check this point?