Sonar scanner failing during Bitbucket Pipelines execution

[ganncamp (G Ann Campbell)]

Hi,

Thanks for sharing the log. I’ll be honest and say I’ve never seen this type of failure before in a SonarQube analysis. It looks like it’s right in the middle of processing the Java files & that’s just not a place for an unexpected EOF to be generated by the analysis itself.

So I searched on the error. This seems to be coming from the container, and it seems to be about the resources available to it. I think this thread should help:

Sonarcloud Bitbucket pipline failing due to exceeded memory limit

This issue is resolved. The problem was not in the amount of memory for the step itself… It was for the Docker process. By default, it is allocated only 1024 MB or memory and for some reason that is not enough in this case. I am not sure why though, but the following link explains how to increase Docker memory https://confluence.atlassian.com/bitbucket/run-docker-commands-in-bitbucket-pipelines-879254331.html#RunDockercommandsinBitbucketPipelines-Dockermemorylimits

 
Ann