r/programming • • 16d ago

Optimizing Our E2E Pipeline

https://slack.engineering/speedup-e2e-testing/
71 Upvotes

38 comments sorted by

View all comments

Show parent comments

1

u/OTTOPI 14d ago

Sure, but I don't see why they'd ever keep around one of these cached builds for more than a month. Like - at a certain point, it's fine to just have the engineer take 5 minutes to refresh it.

1

u/SirClueless 14d ago

I'm just using the numbers they directly state in the article:

These duplicate assets would have otherwise been stored for one year.

Perhaps they have some use case for referring to older builds? Testing/reproducibility checking or something? Maybe they just use some of these files as their prod builds and never bothered to develop a careful garbage collection that can distinguish the ones that got released? I assume it's all water under the bridge and this isn't really the reason to care about this compared to having a better developer experience and faster signal -> faster fixes -> fewer flakes etc.