58 bytes, text/x-review-board-request
Per bug 1303153, there is a lot of older tasks that were created to expire after 1 year, before we changed that policy. Those can be deleted directly in S3 without touching the Artifacts table, for efficiency. Greg, I'll wait on your go-ahead for this.
Email has been sent to dev-platform to inform them of the potential change. Will give a couple of days for people to respond with objections before sending out final notice and taking action on this.
Per :bz, 28 days would be better, and we should adjust the retention times to that level.
Summary: delete old (> 14 days) try, try-bb artifacts from taskcluster-public-artifacts → delete old (> 28 days) try, try-bb artifacts from taskcluster-public-artifacts
To summarize some of the steps that are needed: 1. update mozharness to default artifact expiration to 28 days for Try pushes 2. Update in-tree taskcluster scheduling to use 28 days for try pushes 3. Scan azure for tasks that were the result of a try push, delete if older than 28 days
Attachment #8804395 - Flags: review?(garndt) → review?(dustin)
Comment on attachment 8804395 [details] Bug 1304180 - Set taskcluster artifact expiration to 28 days on try https://reviewboard.mozilla.org/r/88396/#review87500 Well, that was easy, eh?
Attachment #8804395 - Flags: review?(dustin) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/746a12130dc6 Set taskcluster artifact expiration to 28 days on try r=dustin
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla52
You need to log in before you can comment on or make changes to this bug.