Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

bitbucket pipelines skipping upload for existing cache

wade May 14, 2025 edited

yml 

image.png image.png

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? 

 

1 answer

1 accepted

0 votes
Answer accepted
Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 18, 2025

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

wade May 18, 2025

yes.

thanks.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
atlassian, forge, forge learning path, atlassian learning, cloud app development, forge app development, build forge apps, atlassian certification, developer training, jira app development, confluence app development, automation, ui frameworks

Turn Ideas into Atlassian Apps 📱

From setup to deployment—this learning path shows you how to build your first app using Forge. Learn the essentials, streamline workflows, and bring custom solutions to life across Jira, Confluence, and more.

Start Learning
AUG Leaders

Atlassian Community Events