I understand the Gradle daemon is still considered somewhat experimental, but I believe the plan is for it to be enabled by default at some point. If so, I would like to see a lot more documentation on how it behaves, especially in a CI use case with multiple users running multiple builds on the same box.
Here are a few questions I have so far: 1. Will it be recommended to use the daemon on a CI server? 2. Can a single daemon process be shared among builds? i.e. Can concurrent builds use the same daemon process? 3. Is the daemon Gradle-version agnostic, or does there need to be a daemon process per Gradle version? If so, does Gradle handle this automatically? 4. When a daemon process has an issue what happens? Do all subsequent builds fail until you do a --stop? Does it automatically kill and restart? Obviously you can’t account for everything, but are there any specific things that are handled or planned to be handled?
I’ve only done some minor testing on my local machine; I don’t know how much of this is obvious once you’ve used it for a while.