1304180 - delete old (> 28 days) try, try-bb artifacts from taskcluster-public-artifacts

Status: RESOLVED FIXED

(Taskcluster :: General, defect)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

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.

Comment 1

[Greg Arndt [:garndt]]

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.

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

Per :bz, 28 days would be better, and we should adjust the retention times to that level.

Comment 3

[Greg Arndt [:garndt]]

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

Comment 4

[Brian Stack [:bstack]]

Attachment: Bug 1304180 - Set taskcluster artifact expiration to 28 days on try

Review commit: https://reviewboard.mozilla.org/r/88396/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/88396/

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

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?

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/746a12130dc6
Set taskcluster artifact expiration to 28 days on try r=dustin

Comment 7

[Phil Ringnalda (:philor)]

https://hg.mozilla.org/mozilla-central/rev/746a12130dc6