ci: Use predictable cache keys for ccache #29
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.
Problem: Every build always produced a new
ccache
cache tarball with a new cache key, regardless of whether a commit caused the compiled output to change.Solution: Remove the timestamp from the
ccache
cache keys, and replace it with a hash of (some reasonably useful subset of) the files that dictate the build dependencies. This will prevent builds from pessimistically caching and frequently evictingmain
caches.