-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import cache from gradle/gradle-build-action@v2 #48
Comments
There even seems to an error at the end of the first log, that suggests some of the cache keys are the same:
|
The cache protocol has changed with But the extracted cache entries for dependencies etc may have the same cache key, so they won't always be replaced in the cache, even if they are recreated locally. The subsequent runs will reuse these cache entries. It's important that we can continue to evolve the cache protocol for this action, and occasionally updating to a new version of the action will result in the old cache entries not being reused. At this stage there are no plans to support migration of one cache protocol to another. |
I saw that gradle/gradle-build-action@v2 recommends migrating to gradle/actions/setup-gradle instead. They both have caching, but the first run after changing from the old solution to this one does not have any cache:
I am assuming there are going to be a lot of people migrating over to this action, so being able to read the old cache if no new cache has been created yet would save a lot of CI minutes.
The text was updated successfully, but these errors were encountered: