mirror of
https://github.com/gradle/gradle-build-action
synced 2024-11-27 20:12:22 +00:00
76ea8a76b2
Instead of using a fallback strategy to locate a configuration-cache entry based on the current job and git SHA, these entries are now keyed based on their file content with the keys persisted in the primary Gradle User Home entry. This removes the chance of having a configuration-cache entry restored that is incompatible with the restored Gradle User Home state, and makes the logic easier to understand. This change involved a fairly major refactor, with the CacheEntryExtractor being split out from the primary cache implementation, and adding a separate extractor implementation for configuration-cache. |
||
---|---|---|
.. | ||
codeql-analysis.yml | ||
dev.yml | ||
failure-cases.yml | ||
integTest-action-inputs.yml | ||
integTest-caching-config.yml | ||
integTest-caching-configuration-cache.yml | ||
integTest-caching-gradle-home.yml | ||
integTest-caching-java-toolchain.yml | ||
integTest-execution-with-caching.yml | ||
integTest-execution.yml | ||
integTest-gradle-user-home.yml | ||
integTest-gradle-versions.yml | ||
integTest-sample-gradle-plugin.yml | ||
integTest-sample-kotlin-dsl.yml | ||
pr-build-scan-comment.yml |