Alternate cleanup strategy for build tests.#272
Conversation
|
Based on this part of the log, it looks like we pull back 3.8GB just by cleaning up Flatpak. |
|
As an extension of this idea, I don't think much of [edit] and wherever the android emulator gets downloaded |
True... We seem to have avoided the immediate problem right now; perhaps it might be worth turning this into a feature on Briefcase? We've had a suggestion of a |
|
beeware/briefcase#1859 is already tracking the "clean" idea; I've added more details there. |
|
There's been at least 1 failure in this cleanup on Android: This will be because the Gradle daemon is still running, and has open references to some of the files we're trying to delete. If this happens again, it can probably be worked around by adding something like this before the |
An alternate approach to #271.
Instead of pre-emptively deleting Android NDK (and other) content, clean up builds and other caches after each build. Docker builds were already being cleaned up; this gives another layer of cleanup.
PR Checklist: