Multiple restore-keys about drone-cache HOT 3 OPEN

I'll use GitHub's cache action as an example. Read up on the feature here.

You do this:

restore-keys: |
  npm-feature-${{ hashFiles('package-lock.json') }}
  npm-feature-
  npm-

Which evaluates to (for example):

restore-keys: |
  npm-feature-d5ea0750
  npm-feature-
  npm-

When npm-feature-d5ea0750 cache is found, it will be restored, but since it's the first key, the cache will not be rebuilt. In effect it means the package-lock.json has not changed and the cache is fine.

When npm-feature- (which is really npm-feature-*) is found, then the cache is restored, but it also will be rebuilt. This would be the case when the package-lock.json file(s) have changed, which means some dependencies have been updated or changed, so then the cache needs to be rebuilt.

from drone-cache.

Still needed 😄

Rebuild cache should only run when the primary restore key is not hit. That way I can calculate restore key based on dependencies and it will change only when dependencies change.

from drone-cache.

@timbze Thanks for letting us know. I'd have to know more about the use case to better understand how to implement this. If anyone wants to volunteer for taking this on let me know, otherwise it will probably fairly low priority on the list of Drone Cache related work for me, personally.

from drone-cache.