I also wonder about the following statement in the user guide: “If the daemon process is currently busy running some job, a brand new daemon process will be started.”
That presents other implications and questions. From: Luke Daley [mailto:luke.da...@gradleware.com] Sent: Wednesday, July 30, 2014 3:30 PM To: dev@gradle.codehaus.org Subject: Re: [gradle-dev] Gradle daemon on a CI server Official stance is that this is not a good idea. It’s difficult to guarantee stability of a JVM that continuously unloads 3rd party code. If anything you use in your build leaks memory the daemon will eventually choke. I wouldn’t recommend this. On 31 July 2014 at 8:02:36 am, Lóránt Pintér (lorant.pin...@prezi.com<mailto:lorant.pin...@prezi.com>) wrote: Hi, What is the official stance about using the Gralde daemon in a CI server environment? I couldn’t find any useful info on this. I’m looking for ways to make our builds faster, and this seems like a low hanging fruit, but I’m afraid it will cause hard to debug problems. If this is an okay thing to do, are there any recommendations on things like JAVA_OPTS for the daemon, etc? Thanks. -- Lóránt Pintér Developer at Prezi<http://prezi.com>
