Action should not stop gradle deamons started by other runners on a shared host

[milis92]

Stoping Gradle daemons on self-hosted non-ephermal runner is currently canceling Gradle tasks that run in other jobs or workflows even.

This is caused by the post-action step that's stoping all running daemons.

gradle-build-action/src/setup-gradle.ts

Line 103 in 7f46dbd

async function stopAllDaemons(gradleHomes: string[]): Promise<void> {

[bigdaz]

At the moment, we run gradle --stop for all Gradle versions run during the build. If multiple runners on a host share the same Gradle User Home, then this will result in stopping Gradle steps running concurrently.

While it may be considered back practise to share Gradle User Home between different runners on a host, we should avoid stopping the Gradle Daemon when the Gradle User Home directory already exists at the start of the job (in which case we don't attempt to save/restore the Gradle User Home).

[i-walker]

We've experienced this issue with 2.2.1 in several PR's with similar stack-traces like this one https://github.com/arrow-kt/arrow/runs/7498667115?check_suite_focus=true, where the Deamon is cancelled without the task being finished

[bigdaz]

@i-walker That appears to be an unrelated failure. This issue is about the daemon being stopped after the build completes, whereas your issue is that the daemon is stopping/crashing during the build.

See gradle/gradle#19750 for a possible cause of this issue.

[i-walker]

Thank you @bigdaz :D I think that was the issue