Sonarcloud complaining of code smells and stuck on sonarscanner step for a longer time


Our development team is facing issue with the SonarScanner which we have included in our pipeline step. Recently, this issue has came by, the sonar step where we are using sonarsource/sonarcloud-scan:1.4.0 image and it is running from a longer period of time. Ultimately we get an error related to the eslint bridge and our analysis gets failed.

Please team help on this if anyone has faced this issue in last couple of weeks.

1 Like

Hey there.

It looks like you’re running the analysis in Bitbucket Pipelines. Can you share how your Bitbucket Pipelines YML file is configured?

It is configured as part of script inside the bitbucket pipelines

Hey there.

It would be helpful if you shared the full Bitbucket Pipelines YML file, rather than just a screenshot of a snipet.

And, I’d like to know why you’re setting SONAR_SCANNER_OPTS and -Dsonar.javascript.node.maxspace to such high values. There’s a chance that you’re far exceeding what Bitbucket can support memory-wise. What led you to set these values?