Closed
Bug 1303214
Opened 7 years ago
Closed 7 years ago
Expire uploaded taskcluster artifacts (uploaded from BB by Mozharness) in try at 28 days
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Release Engineering
Applications: MozharnessCore
Tracking
(firefox52 fixed)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox52 | --- | fixed |
People
(Reporter: garndt, Assigned: bstack)
References
Details
Attachments
(1 file)
Mozharness currently creates artifacts with a default of 52 weeks, but for Try this could be shortened greatly. For taskcluster tasks we have adjusted this to be 14 days for Try jobs and 1 year for everything else.
Comment 1•7 years ago
|
||
Btw how does this apply to builds and test packages which are part of the index? I assume those live forever? Or are those also getting removed after 1 year, and we still have to rely on archive.mozilla.org as the one and only true archive solution for now?
Comment 2•7 years ago
|
||
Henrik, indexes expire when the task does (well, in theory.. in practice, never). Greg's talking about artifact expiration. Greg, to be clear, you're suggesting changing the *explicit* expiration of tasks uploaded by mozharness, rather than the queue's default.
Summary: Default expiration of taskcluster artifacts to 14 days → Expire uploaded taskcluster artifacts in try at 14 days
Comment 3•7 years ago
|
||
Please let the gecko decision expiration dates higher in order that developers be able to add new jobs beyond 2 weeks. The 'add new jobs' feature on Treeherder depends on it. Thanks.
Comment 4•7 years ago
|
||
Armen, there are no decision tasks for these -- they are Buildbot jobs.
Summary: Expire uploaded taskcluster artifacts in try at 14 days → Expire uploaded taskcluster artifacts (uploaded from BB by Mozharness) in try at 14 days
Reporter | ||
Comment 5•7 years ago
|
||
Sorry for not being clearer, I opened this bug against mozharness and only am referring to the explicit artifact expiration that is set by mozharness when creating the artifact, which is set here: https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/mozharness/mozilla/taskcluster_helper.py#96 I'm not suggesting changing this for anything other than Try. For TaskCluster we have determined that after 14 days, most artifacts are no longer needed for try jobs. I hope this to be the same for the artifacts uploaded using mozharness from Buildbot.
Reporter | ||
Updated•7 years ago
|
Summary: Expire uploaded taskcluster artifacts (uploaded from BB by Mozharness) in try at 14 days → Expire uploaded taskcluster artifacts (uploaded from BB by Mozharness) in try at 28 days
Reporter | ||
Comment 6•7 years ago
|
||
Confirmed with bz on the dev-platform list that 28 days for try artifacts should be acceptable.
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → bstack
Comment hidden (mozreview-request) |
Assignee | ||
Updated•7 years ago
|
Attachment #8802209 -
Flags: review?(garndt)
Reporter | ||
Updated•7 years ago
|
Attachment #8802209 -
Flags: review?(garndt)
Assignee | ||
Updated•7 years ago
|
Attachment #8802209 -
Flags: review?(rail)
Comment 8•7 years ago
|
||
mozreview-review |
Comment on attachment 8802209 [details] Bug 1303214 - Change Mozharness Taskcluster artifact expiration to 28 days https://reviewboard.mozilla.org/r/86506/#review86032
Attachment #8802209 -
Flags: review?(rail) → review+
Pushed by garndt@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7854c40a5797 Change Mozharness Taskcluster artifact expiration to 28 days r=rail
Comment 10•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/7854c40a5797
You need to log in
before you can comment on or make changes to this bug.
Description
•