Closed alclonky closed 4 years ago
@alclonky I'm not a Gradle user or expert but are you able to experiment with adding /home/ubuntu//.gradle/gradle.properties
to your running container containing org.gradle.daemon=false
and confirm if that prevents the problem? Or the env variable might be easier:
@viceice @JamieMagee @ikesyo any opinions? We don't seem to be using GRADLE_OPTS
yet so could set that easily.
@rarkins the daemon should already be disabled for our gradle docker images. So passing the env looks easier band will work for global tools too
@viceice do you mean disabled for our renovate/gradle
images but not for renovate/renovate
?
Yes I think so, have not verified it
The renovate/gradle
container contains all the following in gradle.properties
:
org.gradle.parallel=true
org.gradle.configureondemand=true
org.gradle.daemon=false
org.gradle.caching=false
Should we have all of them for renovate/renovate
too?
We should do it while install gradle with our buildpack, so it will work transparently
looks good in whitesource/renovate:1.0.1
Thanks for confirming. I’ve addd it manually there as is done in renovate/gradle, but we still need a universal solution here in the buildpack.
@rarkins Do we prefer GRADLE_OPTS
env or gradle.properties
file ?
@rarkins Do we prefer
GRADLE_OPTS
env orgradle.properties
file ?
I think go with env if they are otherwise equal
I'm thinking of passing GRADLE_OPTS
as extra env from renovate bot to exec function, so gradle will use them on tests and global too execution 🤔
What Renovate type are you using? whitesource/renovate
Describe the bug
Renovate startes an gradle daemon for each repository with gradle inside (same gradle version is reused, different version stays running)
gradle can be started without daemon (the daemon will be ended after run) https://docs.gradle.org/current/userguide/gradle_daemon.html