We are using Gradle Daemons in our Jenkins builds. But we are experiencing consistent issues where daemons are killed as soon as the Jenkins build, which started them, ends. This is in turn causes other Builds, which reused these Daemons, to fail.
Is there a way to decouple the Daemon process from the Jenkins process? If not, what are the recommended best practices for using Gradle daemons with Jenkins?
We have exactly the same issue.
Therefore, we would appreciate an official response by the Gradle-Team.
Thanks!
I doubt the Gradle team will have much to contribute here.
If the Gradle daemon is killed by Jenkins and should not, you probably need to ask Jenkins about it I guess.