Job Summary shows many unrelated projects on self-hosted runner

[nnellanspdl]

Please see example screenshot below. This is just a small snippet, there are hundreds of projects listed here. This happens for each of our builds.

We use self-hosted runners that are long-lived / not ephemeral.

Two of my initial thoughts are a cluttered cache, or a cluttered gradle home.

I've tried to resolve the gradle home issue by running the following first in my workflow:
rm -rf ~/.gradle
However, this doesn't change anything for me.

[bigdaz]

@nnellanspdl Each Gradle build writes a results JSON file to $RUNNER_TEMP/.build-results.
The action then iterates over these to generate the job summary.

I guess we should either clean these up after the job completes, or make the directory unique for a Job invocation.

Pending a fix in the action, you can ensure that $RUNNER_TEMP/.build-results is cleared after each job. You shouldn't need to remove the ~/.gradle directory.

[nnellanspdl]

Clearing that worked, thanks!

[bigdaz]

This is still something we should address in the action implementation.

[bigdaz]

Fixed in #133