Scanning a repository takes a while but after retrying 2 or more still analysis failed this scan of from Github going to sonarcloud.
Analyze project then import from organization. We are migrating from sonarqube community edition from Sonar Cloud Team Plan. The repository was working in Sonarqube Community but in Sonar Cloud it got stuck somewhere else.
Fix by just enabling sonar.jasmin.internal.disabled=true seems like there is a problem when scanning the repo with new security i just want to know if there is a fix on these moving forward
Hey @kennethg-slph ,
Excuses for the delayed response and for the disruption you experienced. Good that you found a temporary workaround.
We’ve worked extensively on improving the performance of this new JS/TS taint analyzer and a new version should be deployed soon. I’ll update you when it’s done so that you can try it as sonar.jasmin.internal.disabled might be removed in the near future.