Azure Pipelines failed with 403 http error code

SonarQube Cloud
1

Hi
We have few pipelines that uses Azure DevOps extentions which include 3 standard tasks for Sonarcloud;
The first task “SonarCloudPrepare@1” uses the service connection to prepare sonar environment.
I verified the service connection is working and also re-generated its token in sonarcloud portal.
The username behind the service connection (token) is an organization member/admin/owner. So, it has access to all projects.
The first task which is “SonarCloudPrepare@1” completes successfully, being able to fetch project name and key and necessary configuration.
However, second task which is “SonarCloudAnalyze@1” fails somewhere in between, when downloading plugins;
I enabled debug and it shows 403 access denied to download packages.
I share few of them here:

GET 403 https://scanner.sonarcloud.io/plugins/dbdjavafrontend/versions/47edc56f792566bb98eeb29f4332fdf3.jar.gz | time=500ms

GET 403 https://scanner.sonarcloud.io/plugins/dbdpythonfrontend/versions/4b6c81fa66f807eedd228c113293fea8.jar.gz | time=781ms

I also get this generic error msg with each 403 errors saying “ERROR: Project not found. Please check the ‘sonar.projectKey’ and ‘sonar.organization’ properties, the ‘SONAR_TOKEN’ environment variable, or contact the project administrator”

As far as I know, the whole environment and token should be configured in first task “SonarCloudPrepare@1” automatically, and it was working fine up to 2 days ago.

Can you please help me troubleshoot this?

Thanks
Kevin

2

Hey there.

This should be fixed as of a few minutes ago. Can you run a new analysis?

3

OMG, I just re-run the pipeline and it worked;
It took almost 1 day for me troubleshooting this and it ends up to be a service issue!
I should have checked incidents history page earlier.
Thanks

4

Thanks for your patience while we resolved the issue. Don’t hesitate to subscribe to updates on our StatusPage.