Hi,
I have changed a project from CI based (GitHub action) analysis to Automatic analysis.
The Analysis methods page shows that Automatic Analysis is recommended and when I click the switch to enable it, a message appers notifying me that an analysis will start soon.
But the analysis does not start. I have made some commits to GitHub but that also fails to trigger the analysis.
What can I do? I would prefer not to remove the project and add it again.
Hey @stefan-vc!
Can you check in your project Administration > General Settings > Repository Binding that your project is bound to the correct repo?
I can only reproduce the behavior you’re describing if I take some “messy” action, like changing the repos the SonarQubeCloud GitHub Application has access to (removing permissions to the repo I switch to Automatic Analysis). At this point I see no repo bound to my project.
This could happen in other ways as well, like if the SonarQubeCloud app was uninstalled from your organization.
In any case, checking this area of your project administration should make it clear.
Hey @stefan-vc!
Thanks for following up. Looking into the backend (based on the screenshot you shared, which helped me clue into the logs for the right repo), your analyses were failing this morning with a message:
ERROR: Issue exclusions are misconfigured. File pattern is mandatory for each entry of ‘sonar.issue.ignore.multicriteria’
However, now the logs are showing that analysis is succeeding. Can you confirm?
I would have expected that this push a clearer error to the UI (at least not leaving it looking as if nothing happened), but there’s one specific case I"ll have to try and reproduce myself tomorrow.
Hi,
I ended up deleting the project and readded it to sonar cloud.
Thanks for the follow-up. I would guess that you had some invalid issue exclusions.
This should have led to an analysis warning on your project.
However in my tests – the analysis warning shows up and then disappears on refresh. I’m going to escalate this internally.
@stefan-vc We’ve fixed the issue with the API that led to this confusing experience. Thanks a lot for reporting it.
Hi Colin,
Could you take a look on my project again.
I get this error:
Last analysis failed Analysis ID “AZVbaJN1_TRCRSxAeH40”
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: “AZVbaJN1_TRCRSxAeH40”.
I found the issue. I was missing a pattern on a “Ignore Issues on Multiple Criteria”.
