Closed Bzomak closed 1 year ago
We try to cache the Oolite build for use in building the installers. These are usable only within the current workflow run. However, they are still stored and take up space in our GitHub cache allocation.
Add a post-build step, scheduled to run regardless of the Oolite build step success rate, that clears up the Oolite build caches using gh cache command as suggested in https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#managing-caches
gh cache
Fixed by f7fdcc51c0bec4a028140efdae35c1c246167fd1
Current situation
We try to cache the Oolite build for use in building the installers. These are usable only within the current workflow run. However, they are still stored and take up space in our GitHub cache allocation.
Proposed Solution
Add a post-build step, scheduled to run regardless of the Oolite build step success rate, that clears up the Oolite build caches using
gh cache
command as suggested in https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#managing-caches