GitHub repo runs SonarCloud analysis automatically as part of the PR review process.
SonarCloud Analysis automatic code analysis checks started failing today for certain GitHub project but we didn’t change anything.
The analysis error in SonarCloud said to raise a ticket here.
Pull Requests in GitHub show that SonarCloud checks didn’t seem to run.
There are no checks for this commit
Some checks haven’t completed yet, 1 expected check
SonarCloud Code Analysis Expected — Waiting for status to be reported
In SonarCloud, under “Pull Requests”, we are seeing the new pull requests with a message “The last analysis has failed”. Clicking the See Details shows the message about posting here.
We’ve encountered some issues with our JS/TS analyzer since the start of this week.
In brief, our JS/TS analyzer required additional memory, leading us to enhance the capacity of our Automatic Analysis workers.
It appears that your analysis has been functioning smoothly following our corrective measures. Should you require further assistance, please do not hesitate to reach out.
Thank-you for sharing regarding the JS/TS analyzers.
Since the update, the JS/TS analyzers are now running again, however, we have noticed that warnings are being reported that weren’t present before.
Last analysis has warnings
There were parsing errors in 65 files while analyzing the project. Check the logs for further details.
We’ve not been able to find the logs mentioned within SonarCloud.
Sample Analysis ID : AY12QuSMjsDsqf8rreqD
Where are the logs located in SonarCloud?
Are the JS/TS analyzers running correctly?
After the fix was applied, we continue to see new parsing warnings reported that weren’t present before.
Sample Analysis ID : AY2pSRhw-B8uoLD7t_Zc
Last analysis has warnings
There were parsing errors in 75 files while analyzing the project. Check the logs for further details.
We’ve NOT been able to find the logs mentioned within SonarCloud.
Where are these logs located in SonarCloud?
–
Within SonarCloud , we reviewed the Administrator → Backend Tasks area within an affected project and found that the “SonarScanner Context” shows that the SonarCloud plugin for JavaScript/TypeScript/CSS may NOT be running as it is missing in the Plugins list in newer scans.
We’ve noticed that the parsing warning count grows as the number of files of the type (TypeScript, JavaScript, CSS and VUE) grow within the affected projects.
Even though Sonar scans are reporting passing :
It is concerning that these new warnings are being report in conjunction with the missing plugin “JavaScript/TypeScript/CSS Code Quality and Security 10.10.0.24774 (javascript)” in SonarScan Context history for newer scan (since the fix was applied).
Are the JS/TS/CSS analyzers running and if so are they running successfully & correctly?
Thank you for submitting your report, and a warm welcome to the Sonar community!
The support for Vue.js analysis within the context of SonarCloud’s automatic code analysis is currently limited.
Upon reviewing your logs, it appears that your project relies on the Vue.js TSConfig from the dependency @vue/tsconfig. However, during automatic analysis for JS/TS, external dependencies are missing, including @vue/tsconfig. Consequently, TypeScript fails to compile your project and is not able to parse files from your codebase because the TSConfig your project extends is missing.
As suggested by one of my colleagues in a similar report, a viable workaround is to manually copy the contents of @vue/tsconfig into your TSConfig until this limitation is addressed.
