SonarCloud check not triggered in CI

Hello,

In our project, the SonarCloud analysis in GitHub Actions often gets canceled with this message:

However, when we open the PR page on SonarCloud.io, we see the message but no button to re-run the analysis manually.

Can you please check this with us ?

Thanks!

Hey there.

Can you paste that Analysis ID here? :slight_smile: Thanks.

Hello,

Yes of course : AZhWDcgzVOaN5q397Am4 :grin:.

Best regards,

Hello,

This particular analysis failed with this error:

Report for commit 'b30be597aec3a8674b61ef2410415a7bdce039b8' can’t be processed: a newer report has already been processed, and processing older reports is not supported. The last processed report was for commit 'b30be597aec3a8674b61ef2410415a7bdce039b8'.

Just for information, you can see the error on the Background Tasks page of your project on SonarQube Cloud.

It means that several commits were merged on the same branch very closely one after the other. Their CI pipeline ran simultaneously, and the reports have been submitted in the reverse order.

Sadly, this is not something we can do anything about. It doesn’t impact the results shown in the SonarQube Cloud UI, since the analysis of the last commit took into account the previous commits too.

About the message that mentions a retry, I agree it is confusing, as the analysis can’t be retried without a rerun of your CI pipeline or a new commit. I’ll share this with the team in charge of that part of the software to improve it.

Best,

Hello @bousselham-mhidi

As Claire explained, there is not much we can do when multiple analysis for the same PR reach SonarQube Cloud in the wrong temporal order. It’s rare but it happens, and above all this should be handled and the CI level.

However we created a ticket to change this error message which is confusing. We will make explicit that a new analysis (ie. a new Pipeline) will have to run.

Cheers

Antoine