Sonar not reporting final success status to GitHub

SonarQube Cloud
1

Sonarcloud no longer decorates the PR after a scan of all analysis after the 13th march 2025.
Also branch analysis is no longer reported for branches.
On Sonarcloud site, reports shows as completed and they are updated.

  • ALM: GitHub
  • CI system used: Jenkins CI
  • Scanner command:
mvn sonar:sonar
-Dmaven.repo.local=_somedir_/PR-1854/.m2/repository 
-Dsonar.coverage.jacoco.xmlReportPaths=_somedir_/PR-1854/_somedir_/jacoco-report/target/report-aggregate/jacoco.xml 
-Dsonar.organization=_someorg_ 
-Dsonar.pullrequest.base=develop 
-Dsonar.pullrequest.branch=_somebranch_
-Dsonar.pullrequest.key=1854 
-Dsonar.pullrequest.provider=GitHub 
-Dsonar.pullrequest.github.repository=_somerepo_
  • Languages: Java
  • Private repository
  • Error observed: Github check of “Sonar Code Analysis” remains in “Expected — Waiting for status to be reported” even if the Sonarcloud portal reports Successfull status and report on Jenkins reports SUCCESS status
  • Steps: every scan after the 13th of March 2025 is not reporting back the final status on the pull request
  • Potential workaround: None

Final log report of Sonar Analysis:

[...]
[INFO] 11:49:39.166 Reading SonarArchitecture IR data from directory "_somedir_/PR-1854/_somedir_/target/sonar/architecture/js"
[INFO] 11:49:39.166 * Protobuf reading complete | memory total=1234 | free=508 | used=725 (MB)
[INFO] 11:49:39.166 * Export complete | memory total=1234 | free=508 | used=725 (MB)
[INFO] 11:49:39.166 Sensor JsArchitectureSensor [architecture] (done) | time=1ms
[INFO] 11:49:39.166 Sensor Zero Coverage Sensor
[INFO] 11:49:39.183 Sensor Zero Coverage Sensor (done) | time=17ms
[INFO] 11:49:39.183 Sensor Java CPD Block Indexer
[INFO] 11:49:40.132 Sensor Java CPD Block Indexer (done) | time=949ms
[INFO] 11:49:40.136 SCM Publisher SCM provider for this project is: git
[INFO] 11:49:40.137 SCM Publisher 1 source file to be analyzed
[INFO] 11:49:40.543 SCM Publisher 1/1 source file have been analyzed (done) | time=406ms
[INFO] 11:49:40.629 CPD Executor 624 files had no CPD blocks
[INFO] 11:49:40.630 CPD Executor Calculating CPD for 972 files
[INFO] 11:49:40.814 CPD Executor CPD calculation finished (done) | time=184ms
[INFO] 11:49:40.994 SCM writing changed lines
[INFO] 11:49:41.067 SCM writing changed lines (done) | time=73ms
[INFO] 11:49:41.193 Analysis report generated in 328ms, dir size=1 MB
[INFO] 11:49:41.882 Analysis report compressed in 689ms, zip size=1004 KB
[INFO] 11:49:42.604 Analysis report uploaded in 722ms
[INFO] 11:49:42.605 ANALYSIS SUCCESSFUL, you can find the results at: https://sonarcloud.io/dashboard?id=_someproject_&pullRequest=1854
[INFO] 11:49:42.605 Note that you will be able to access the updated dashboard once the server has processed the submitted analysis report
[INFO] 11:49:42.606 More about the report processing at https://sonarcloud.io/api/ce/task?id=_someid_
[INFO] 11:49:42.612 Time spent writing ucfgs 0ms
[INFO] 11:49:42.753 Analysis total time: 1:09.696 s
[...]
2

Hey there.

Looking in the backend, SonarQube Cloud is getting a 404 when checking if the SonarQube Cloud application is installed on your org, and has access to your repo.

Can you check that:

3

Hi Colin,

Thanks for the reply.

Asked my IT to check both points and they confirmed they are ok.

They found a permission issue on GitHub side and now we have back the comment by Sonarcloud with the analysis result.
We are still not having the updated status on the GitHub checks. ITs is still investigating.

Any suggestion where to look?

Thanks,

Alberto

4

I will reach out to you via a private message to gather some additional details and see if we can help track down the issue.

1 Like
9

Issue solved on our side.

Not sure about what fixed it.
It started to work again after few days after opening this thread.

1 Like
12

I’d have to guess a transient issue from GitHub. Thanks for reporting it anyways. Glad it’s all working now.