Smarter Caching on Github Actions #2788
Merged
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.
Currently our Github Actions setup relies on a static key for caching.
This means that we restore an old Gradle cache that doesn't contain the version of Gradle we need (it gets re-downloaded every time).
Given that we don't have a lockfile (should we consider it?), I'm hashing 'buildSrc/src/main/kotlin/Versions.kt' and adding it to the cache key. So the cache will be partially invalidated whenever we release a new version (or whenever we bump a library).