-
Notifications
You must be signed in to change notification settings - Fork 555
Closed as not planned
Labels
bugSomething isn't workingSomething isn't workingneeds-triageIssue is not approved or ready-to-work onIssue is not approved or ready-to-work on
Description
📜 Description
We have a pipeline where builds continuously fail because the cache size is too big.
Looking over the build history we can see how in a period of one month it grew from around ~400Mb to a staggering size of almost 4Gb
It grows in size, until it's too big and the build fails, then we have to run the build manually without cache, so it shrinks again for a while before it grows once more. We have to repeatedly do this.
👟 Reproduction steps
I'm not sure. I don't know if this is a unique situation because our repository is large to begin with (monorepo), or something else.
👍 Expected behavior
Cache should be pretty consistently the same size.
👎 Actual Behavior
Cache grows in size seemingly to no end.
☸ Kubernetes version
1.32
Cloud provider
AWS
🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?
- I checked and didn't find any similar issue
🏢 Have you read the Code of Conduct?
- I have read the Code of Conduct
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingneeds-triageIssue is not approved or ready-to-work onIssue is not approved or ready-to-work on



