https://kotlinlang.org logo
#gradle
Title
# gradle
j

Joseph Hawkes-Cates

09/25/2023, 9:11 PM
I am trying to speed up our CI builds and one thing I found was that using the Gradle Daemon can help. We have never explicitly disabled the daemon for our builds, but I see the log below happening in each one:
Copy code
To honour the JVM settings for this build a single-use Daemon process will be forked. See <https://docs.gradle.org/8.0/userguide/gradle_daemon.html#sec:disabling_the_daemon>.
Daemon will be stopped at the end of the build
Is there anything we can do to enable the Gradle Daemon in these builds or can someone confirm if this is even worth pursuing?
not kotlin but kotlin colored 1
I did try explicitly adding
--daemon
to the build commands, but still see this log
v

Vampire

09/25/2023, 9:14 PM
It has its pros and its cons. And also depends e. g. on whether you have persistent build agents, or ephemeral build agents, running builds in fresh docker containers. And even then it depends on whether you run only one Gradle command or multiple ones.
If that message comes it indeed means the daemon is disabled. You can enable or disable it by different means, like
gradle.properties
, system properties, commandline arguments, ...
The command line argument should have precedence, so if you use
--daemon
and still get that message, my best guess is, that your CI server adds
--no-daemon
after your manually configured arguments.
Besides that, your question is off-topic here. Please always consider not only channel names, but also channel topics in open communities like this one.
j

Joseph Hawkes-Cates

09/25/2023, 9:46 PM
Ah sorry, will do. Thanks for the response
👌 1
2 Views