-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Address gradle temp file pollution insanity #14385
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
Comments
I think the hack we had in https://github.com/apache/lucene-solr/pull/1767/files used to work but gradle must have relocated those temp files... The fix is simple but I'd like to do some analysis what exactly happened and when first. |
It's this commit that moved the temp folder from java.io.tmpdir, which we redirected and cleaned up. gradle/gradle@8c2f6b7#diff-a89e26b86bb25dd2df7ef61416478f3b9034cc4625633830a5413a5c5d7124f6 |
Ok, I've added gradle's "user home" tmp cleaning as well. Anything older than 3 hours is removed. This folder may be shared across builds so the time limit is there to prevent accidental cross-build issues. |
There are also *.log files to wipe clean. |
Uh oh!
There was an error while loading. Please reload this page.
Description
Gradle creates temp files it never cleans up. Until this is resolved, let's try to keep some housekeeping ourselves.
Related issues:
The text was updated successfully, but these errors were encountered: