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)

Product:
Release Engineering
Component:
Applications: MozharnessCore
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox52 fixed)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox52 --- fixed

People

(Reporter: garndt, Assigned: bstack)

References

Details

Attachments

(1 file)

Bug 1303214 - Change Mozharness Taskcluster artifact expiration to 28 days
58 bytes, text/x-review-board-request
rail
: review+
Details 
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.
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?
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
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.
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
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.
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
Confirmed with bz on the dev-platform list that 28 days for try artifacts should be acceptable.
Blocks: 1304180
Assignee: nobody → bstack
Attachment #8802209 - Flags: review?(garndt)
Attachment #8802209 - Flags: review?(garndt)
Attachment #8802209 - Flags: review?(rail)
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
https://hg.mozilla.org/mozilla-central/rev/7854c40a5797
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox52: --- → fixed
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.