Allow Gradle daemon to continue running between build steps #113
Comments
|
As of v2.1, the daemon is still disabled, but is done via This means that, pending a fix to this issue, a workflow can provide the |
This should optimize LRU cache eviction so main and branches always have reasonably fresh gradle caches and main does not ever get evicted, since branches have independent caches and would otherwise fill up 10GB cache limit Note that `--daemon` is specified as the default for this action is no daemon, that is correct for long-lived runners to avoid cross-build contamination, but on GitHub Hosted Runners (which we use) we are clean each run, so this is a small optimization to share gradle between steps: gradle/gradle-build-action#113 (comment)
This should optimize LRU cache eviction so main and branches always have reasonably fresh gradle caches and main does not ever get evicted, since branches have independent caches and would otherwise fill up 10GB cache limit Note that `--daemon` is specified as the default for this action is no daemon, that is correct for long-lived runners to avoid cross-build contamination, but on GitHub Hosted Runners (which we use) we are clean each run, so this is a small optimization to share gradle between steps: gradle/gradle-build-action#113 (comment)
This should optimize LRU cache eviction so main and branches always have reasonably fresh gradle caches and main does not ever get evicted, since branches have independent caches and would otherwise fill up 10GB cache limit Note that `--daemon` is specified as the default for this action is no daemon, that is correct for long-lived runners to avoid cross-build contamination, but on GitHub Hosted Runners (which we use) we are clean each run, so this is a small optimization to share gradle between steps: gradle/gradle-build-action#113 (comment)
This should optimize LRU cache eviction so main and branches always have reasonably fresh gradle caches and main does not ever get evicted, since branches have independent caches and would otherwise fill up 10GB cache limit Note that `--daemon` is specified as the default for this action is no daemon, that is correct for long-lived runners to avoid cross-build contamination, but on GitHub Hosted Runners (which we use) we are clean each run, so this is a small optimization to share gradle between steps: gradle/gradle-build-action#113 (comment)
By finalizing with a step running |
|
About adding the |
I'm not aware of an environment variable that does this. I suppose you could write an action that changes Otherwise, I'm afraid that you'll need to wait until this issue is fixed. |
|
Thanks for the fix! Nice to have it now right by default 🙂 |
gradle/gradle-build-action#113 Change-Id: I7f4d52bef6113bde03622e652c4f5596251dbc63
The current implementation uses the
--no-daemonflag to avoid the need to stop daemons at the end of the job. Instead, we should run the build as configured, keeping track of invocations and runninggradle --stopas required at the end of the job.The text was updated successfully, but these errors were encountered: