[SERVER-11289] Put cache for third_party build artifacts in separate directory if possible Created: 21/Oct/13  Updated: 06/Dec/22  Resolved: 03/Feb/18

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Mathias Stearn Assignee: Backlog - Build Team (Inactive)
Resolution: Won't Fix Votes: 0
Labels: build-later
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Build
Participants:

 Description   

I often have to rm -r build/cached/.cache since it fills up my disk quickly. It would be nice if there was a similar command to just kill the mongo stuff since the third_party code doesn't change nearly as often.



 Comments   
Comment by Andrew Morrow (Inactive) [ 03/Feb/18 ]

We now have cache pruning scripts, so this isn't as much of an issue.

Comment by Andrew Morrow (Inactive) [ 04/Nov/13 ]

We might be able to do this if we consistently used a cloned env for everything under third_party. Perhaps then it could have its own CacheDir?

We should also investigate reducing the number of mongo specific flags and options that we pass along to third_party that vary with build flags but don't actually affect the build of the third_party components. This would make it less likely that they get rebuilt.

Generated at Thu Feb 08 03:25:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.