Nebula test and gradle daemon still alive after test execution

Hi all,

I’m using nebula-test for testing my gradle plugin. It uses gradle Tooling API to execute external gradle projects builds. Unfortunately, after test execution, all Gradle Daemons for various gradle vesions, which have huge effect on my computer memory.

Is there any option in Tooling API to kill/stop gradle daemon ? Or to set shorter timeout for inactivity ?



There’s no public API for this.

However, you might be interested to know that we are working on an official version of this kind of thing that will provide options to manage the daemon. The first version will be released soon with Gradle 2.6.