SonarScanner plugin with Gradle 7.2 throws JVM heap space is exhausted on Azure Devops

SonarCloud
, ,
1

Hi, Brains!

I’m running Gradle (7.2) build to build our App (Java) on Azure DevOps. Our code is on Bitbucket Cloud.
So, I’m using Gradle@2 to run the Sonar (plugin 3.3). We are using SonarCloud.io and plus:

sonarQubeRunAnalysis: true
sqGradlePluginVersionChoice: 'build'

I’m attaching examples to build.gradle and azure devops pipeline.

Since then, I’m getting errors like this:

Expiring Daemon because JVM heap space is exhausted
Daemon will be stopped at the end of the build after running out of JVM memory
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted

Could you help me with that guys, please?

build.gradle.txt (3.2 KB)
MyPipeline.yml.txt (1.3 KB)

Kind regards,
Paulo

2

Hi @Paulo_Alexandre_Mach welcome to the community,

Can you check this documentation in order to increase the heap size ?

https://docs.gradle.org/current/userguide/build_environment.html#build_environment

Let us know if it resolves your issue.

Thanks
Mickaël

3

We started having the exact same issue, but in a restricted environment: GitHub Actions. We need basically all the RAM we can get to be able to build and test our application - not much RAM to spare to give it to gradle.