-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Job Summary shows many unrelated projects on self-hosted runner #127
Comments
@nnellanspdl Each Gradle build writes a results JSON file to 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 |
Clearing that worked, thanks! |
This is still something we should address in the action implementation. |
Fixed in #133 |
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.
The text was updated successfully, but these errors were encountered: