Devops error when running analytic build not finding pr, but finding the pr in sonarcloud

SonarQube Cloud
1

running the analytics job weve setup in azure for sonarcloud, running with “bound” project setup

suddenly the analytics jobs fails on

Error during SonarScanner execution
ERROR: Could not find the pullrequest with key '6551'
ERROR: Caused by: Error 404 on https://sonarcloud.io/api/alm_integration/show_pullrequest?project=<proj>&pullrequestKey=6551 : {"errors":[{"msg":"Unable to find the pullrequest with key \u00276551\u0027"}]}
ERROR:
ERROR: Error during SonarScanner execution
ERROR: Could not find the pullrequest with key '6551'
ERROR: Caused by: Error 404 on https://sonarcloud.io/api/alm_integration/show_pullrequest?project=<proj>&pullrequestKey=6551 : {"errors":[{"msg":"Unable to find the pullrequest with key \u00276551\u0027"}]}
ERROR:

have worked fine until this morning? since iam checking on your sonarcloud page the project id and pr id do exist (it was created a week ago) is the api broken?

2

Hey there.

It sounds like the token being used to make the connection between SonarCloud and Azure DevOps is (no longer) valid. Take a look at your project-level Administration > Pull Requests or organization-level Administration > Organization settings > Azure DevOps connectivity management and make sure a valid token is set.

3

done that and validated the token, wouldnt i get an authorization issue

if i use the endpoint
curl https://sonarcloud.io/api/alm_integration/show_pullrequest?project=[proj]&pullrequestKey=6551
with an propper authroization(generated under my account, sonarcloud), it will still return the same result,

as i mentioned i checked the existing pr and the parameters are correct. so it dosent seem like a authroization issue.

4

sorry you were correct, would be more straight forward to do authroization thing about it since apparently the organization token was removed/expired

would be nice to get a more propper authroization error from telling why it cannot fetch the data, in this case it would make more sense to just throw an authroization issue maybe with a hint sonarcloud-azure

ty @Colin