Sonarqube-quality-gate-action started failing with HTTP 404

SonarQube Server / Community Build
1

When running the sonarqube-quality-gate-action as part of our GH actions workflow, we started receiving the following error:

Run sonarsource/sonarqube-quality-gate-action@cf038b0e0cdecfa9e56c198bbb7d21d751d62c3b
  with:
    scanMetadataReportFile: target/sonar/report-task.txt
    pollingTimeoutSec: 300
  env:
    REGISTRY: ghcr.io
    JAVA_HOME: /opt/hostedtoolcache/Java_Zulu_jdk/21.0.10-7/x64
    JAVA_HOME_21_X64: /opt/hostedtoolcache/Java_Zulu_jdk/21.0.10-7/x64
    SONAR_TOKEN: ***
    SONAR_HOST_URL: ***
Run $GITHUB_ACTION_PATH/script/check-quality-gate.sh "target/sonar/report-task.txt" "300"
  $GITHUB_ACTION_PATH/script/check-quality-gate.sh "target/sonar/report-task.txt" "300"
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail ***0***
  env:
    REGISTRY: ghcr.io
    JAVA_HOME: /opt/hostedtoolcache/Java_Zulu_jdk/21.0.10-7/x64
    JAVA_HOME_21_X64: /opt/hostedtoolcache/Java_Zulu_jdk/21.0.10-7/x64
    SONAR_TOKEN: ***
    SONAR_HOST_URL: ***

curl: (22) The requested URL returned error: 404

We are using SonarCloud.

The latest successful build was last last Feb 27th.

Do you know if anything has changed recently?

2

It seems that the reason was related to the temporarily suspension of our organization on SonarCloud.

I was able to find this only by browsing around in the web console: a more thorough error message could have helped, anyway.

Closing.

4

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