yml
doc: https://support.atlassian.com/bitbucket-cloud/docs/cache-dependencies/#Caching-with-file-based-cache-keys
I want to update project_cache when Cargo.lock content changes. However, cache updates are skipped.
how to fix?
G'day, @wade
Welcome to the community!
I think there's a misunderstanding. With Cache keys, changes made in the pipeline build will not invalidate the existing cache. Therefore, what you're observing is expected behavior; the cache will only be invalidated if the changes were made via a commit.
Custom caches can support file-based cache keys. File-based cache keys allow for the generation and restoration of caches based on a set of files. Any changes to those files would result in a new cache.
Basically, changes to the files, in this case Cargo.lock, through commit will then trigger a new cache to be uploaded.
I hope this helps.
Regards,
Syahrul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.