It’s been few hours, and the Automatic analysis is not working. Attaching the screenshot of PR status and Sonalcoud UI status
![]()
![]()
It’s been few hours, and the Automatic analysis is not working. Attaching the screenshot of PR status and Sonalcoud UI status
![]()
![]()
Hi Team,
The issue is only with this particular Github repo. Can you look into this ?
Thanks
Alexy
Now there is an error message shown
Last analysis failedAnalysis ID “db37d24c-d982-4484-845a-9a44a2353488”
Your analysis with ID “db37d24c-d982-4484-845a-9a44a2353488” has failed because it took too much time. Please try another CI tool to analyze your project.
Actually, we are not using any CI tool. We have enabled automatic analysis. So that when a PR is raise to main branch this happens automatically.
Hi,
Sorry for the delay in responding. It looks like our work to flesh-out the automatic analysis errors is bearing fruit, though. ![]()
So what this is telling you is that your project is too large or too complex (or both?) to successfully use automatic analysis. You’ll need to configure analysis in a CI. Since you’re on GitHub, GH Actions is an obvious candidate. The docs should get you started.
HTH,
Ann
Hi,
Thanks for the update! On a lighter note, many developers were reaching out to me to resolve this issue, and I skilfully redirected them by saying @ganncamp would take a look.
Regarding the limitation, could you please clarify if this is a restriction? We successfully added a single file in a PR and the analysis ran fine. However, when multiple files were included—even if consolidated into a single file—the analysis failed to work. We have our code in GitHub but we use Jenkins for our Build setup. Our basic requirement is, the PR check shouldn’t be successful if there are code smells.
Hi,
What language are we talking about here?
Ann
Hi,
All those files are json files.
Alexy
Hi Alexy,
Nothing springs to mind for why you would be seeing this with JSON files. All we can really know without the analysis log (which I don’t have direct access to) is that your analysis is timing out, which makes it time to switch to CI-based analysis.
Sorry I can’t be more help here.
![]()
Ann