ci: Use restore-key to continually update ccache storage #1263
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We observed a brief period of speedup in the CI after introducing ccache, which degraded again after a few weeks:
This is due to the fact that GitHub Actions caches do not get updated at the end of their run. This PR introduces a workaround. The CI will
cache_key_$OS_$JOB_$COMMIT_SHA
and use that if found. If not it willcache_key_$OS_$JOB_
, and use that if found. Otherwise it will perform a build from scratchcache_key_$OS_$JOB_$COMMIT_SHA
). The next CI run will use that cache as a starting point.Clearly, this means that the cache size will continually increase. However, ccache has a maximum size setting, which I set to 2GB in this PR. We'll have to see if that results in a reasonably sized, reasonably up-to-date cache and corresponding fast build times.