The URL of our DevOps organization is different because the DevOps org name changed. The result is that any SonarCloudAnalyze step of our pipeline on PR builds are now failing with errors because the URL has changed.
Specific errors from pipeline logs:
##[error]ERROR: Error during SonarScanner execution
ERROR: Could not find the pullrequest with key '8931'
ERROR: Caused by: Error 404 on https://sonarcloud.io/api/alm_integration/show_pullrequest?project=<REDACTED> : {"errors":[{"msg":"Requested resource wasn\u0027t found on Azure DevOps.","reason":"AZURE_DEVOPS_UNABLE_TO_FETCH_REQUESTED_RESOURCE"}]}
ERROR:
ERROR: Error during SonarScanner execution
ERROR: Could not find the pullrequest with key '8931'
ERROR: Caused by: Error 404 on https://sonarcloud.io/api/alm_integration/show_pullrequest?project=r<REDACTED> : {"errors":[{"msg":"Requested resource wasn\u0027t found on Azure DevOps.","reason":"AZURE_DEVOPS_UNABLE_TO_FETCH_REQUESTED_RESOURCE"}]}
ERROR:
##[error]The SonarScanner did not complete successfully
The SonarScanner did not complete successfully
##[error]19:14:06.04 Post-processing failed. Exit code: 1
19:14:06.04 Post-processing failed. Exit code: 1
##[error]The process '/opt/hostedtoolcache/dotnet/dotnet' failed with exit code 1
We are far from the first team to have run into the same issue. Here’s another recent example: Change Azure Devops link in organization
The problem is that I cannot - as an administrator of our SonarCloud organization - change the base DevOps URL. It’s the same problem as noted in the link above, where an internal Sonar person (Florian) stepped in and was able to “unbind your organization and let you bind it again to the new one”. That is not an option exposed via SonarCloud’s interface as a self-service option.
Thanks,
Annie