Closed Bug 1268862 Opened 4 years ago Closed 4 years ago

Use a shorter artifact lifetime for try jobs

Categories

(Taskcluster :: Services, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED
mozilla49

People

(Reporter: dustin, Assigned: dustin)

References

Details

Attachments

(1 file)

This should be implemented as a taskgraph generation filter, similar to stripping caches, to set try job task and artifact lifetimes to, say, 2 weeks.
Assignee: nobody → dustin
Duplicate of this bug: 1163098
Nick, can you let me know what the current retention times are?
Flags: needinfo?(nthomas)
Historically we've kept try for 2 weeks, as we were limited by NetApp disk availability. Now that we're on S3 it's softer due to the way the billing is aggregated, or the discussions just happen above my level. FWIW, we currently have a lot more for buildbot builds due to an oversight setting up expiration in S3.
Flags: needinfo?(nthomas)
re 2 vs 4 weeks - I don't know that we have any data for 'usefulness' of longer retention. Maybe the http logs for archive.m.o or TC artifacts could do that, or look for repushes somehow. My guess is that most pushes are useful for just a day - they either work, or fail and get superceded fast - with a tail where people come back to projects later. With Treeherder retention being longer the logs are still available in that case, just not the binaries. At any rate lets agree a common value.
Well, it's an in-tree configuration :)

I'll start with 2 weeks, and if users want to bump it, they can (hopefully with some discussion of potential cost).  Also, individual try pushes can be bumped!
Attachment #8749679 - Flags: review?(nthomas) → review+
Comment on attachment 8749679 [details]
MozReview Request: Bug 1268862: expire try jobs in a shorter time-period than default; r=nthomas

https://reviewboard.mozilla.org/r/51093/#review48405

r+ on the 14 day retention, the rest eyeballs OK but I don't claim any background with it.
https://reviewboard.mozilla.org/r/51093/#review48425

::: testing/taskcluster/tasks/decision/try.yml:22
(Diff revision 1)
>    - taskId: '{{#as_slugid}}decision task{{/as_slugid}}'
>      reruns: 3
>      task:
>        created: '{{now}}'
>        deadline: '{{#from_now}}1 day{{/from_now}}'
> +      expires: '{{#from_now}}28 day{{/from_now}}'

Whoops, this should have been 14 days
Comment on attachment 8749679 [details]
MozReview Request: Bug 1268862: expire try jobs in a shorter time-period than default; r=nthomas

Review request updated; see interdiff: https://reviewboard.mozilla.org/r/51093/diff/1-2/
Attachment #8749679 - Attachment description: MozReview Request: Bug 1268862: expire try jobs in a shorter time-period than default; r?nthomas → MozReview Request: Bug 1268862: expire try jobs in a shorter time-period than default; r=nthomas
Yay, and it magically carried forward the r+.  Not sure that's according to policy, but it works for me :)
https://hg.mozilla.org/mozilla-central/rev/79abc7d21209
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
Component: Integration → Services
You need to log in before you can comment on or make changes to this bug.