The last analysis has failed - ID: ff701522-7f3f-4e01-a8a5-8eedfc21a6e6

SonarQube Cloud
1

Hello,

we are using SonarQube Cloud with Automatic Analysis for a GitHub repository. This setup used to work without problems.

Now, on all PRs, GitHub only shows “SonarCloud Code Analysis / Expected — Waiting for status to be reported” and nothing else happens.

In the SonarQube Cloud project overview, we now see this error:

The last analysis has failed. If it keeps on failing after several attempts, please contact us on Community forum and provide the following failing analysis ID: ff701522-7f3f-4e01-a8a5-8eedfc21a6e6

What we already checked:

  • Analysis Method is set correctly to Automatic Analysis
  • The repository is still eligible for Automatic Analysis
  • The GitHub app is installed and configured
  • This used to work before, and we did not intentionally change the SonarQube configuration. We don’t use a .sonarcloud.properties file, just the configuration in sonarqube cloud

Questions:

  • Is there any known issue with Automatic Analysis that could cause this?
  • Can you check the failing analysis ID and tell us why the analysis is failing?
  • Is there anything specific we should verify on the GitHub or SonarQube Cloud side?

Thanks.

2

Hi,

Welcome to the community and thanks for this report!

Here’s the underlying error:

fatal: repository 'https://github.com/CactuseSecurity/firewall-orchestrator-agents/' not found

Has your project structure changed?

 
Ann

3

Hi,

thank you very much for the swift reply. ‘firewall-orchestrator-agents’ is a private sub-repository that is being referenced to via a sym-link (git submodule). However, we have had this for three months already and SonarQube was able to handle (/ignore) it without problems.

Is there maybe a way to hard-ignore parts of the repo in SonarQube?

Or would it be better to give Sonar permissions for the sub-repo?

Thanks.

4

Hi,

I suspect the sym-link was previously ignored, and a recent update meant it started being noticed. I’m not sure that even with permissions this is going to go well. You could try setting exclusions. Otherwise, your best bet is to move to CI-based analysis.

 
HTH,
Ann

8

Hi Ann,

thank you very much for the clarification.

We now switched to CI-based analysis and that is working well so far.