Closed
Bug 1167004
Opened 9 years ago
Closed 8 years ago
gecko: Per branch cache folders for builders (discussion)
Categories
(Taskcluster :: General, defect)
Taskcluster
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jonasfj, Unassigned)
Details
Attachments
(1 obsolete file)
Today we had issue where bugs in one branch affected another branch, because we shared cache folders for object-dir between branches. (This probably only relevant for object-dir caches, not source clones) I'm not sure that is wise, or even efficient. Sure we save space, but we also get a cache that is less likely to be hot. Assuming we don't constantly sync branches (which we do for some). anyways, I suggest that we do per-branch cache folders, so someone forgetting to touch clobber doesn't poison cache folders that other branches use. @mshal, I might be wrong I suspect you know the build system a bit, hence, I cc'ed to to hear if sharing object-dirs between branches is crazy, sane or somewhere in between :)
Updated•9 years ago
|
Component: TaskCluster → General
Product: Testing → Taskcluster
Comment 1•9 years ago
|
||
Bug 1167004 - Use per branch cache for b2g and mulet builders r=jonasfj
Attachment #8646107 -
Flags: review?(jopsen)
Updated•9 years ago
|
Attachment #8646107 -
Attachment is obsolete: true
Attachment #8646107 -
Flags: review?(jopsen)
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•