Selectively Expire Build Artifacts in the public/build Directory
Categories
(Firefox Build System :: Task Configuration, task)
Tracking
(firefox109 fixed)
| Tracking | Status | |
|---|---|---|
| firefox109 | --- | fixed |
People
(Reporter: bxbrenden, Assigned: bxbrenden)
References
(Depends on 1 open bug, Blocks 3 open bugs)
Details
Attachments
(1 file, 3 obsolete files)
Now that we have introduced the ability to selectively expire artifacts based on labels in Bug 1649987 (and modified expiration in Bug 1788708), we need to offer the ability to expire artifacts that land in the public/builds directory.
We will likely not be able to control these at the level of individual artifacts, e.g. public/build/en-US/target.talos.tests.tar.gz but folder-level should be possible, i.e. making sure that everything in public/build expires on a certain date that is before the expiration of the task.
| Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
| Assignee | ||
Comment 2•3 years ago
|
||
| Assignee | ||
Comment 3•3 years ago
|
||
Updated•3 years ago
|
| Assignee | ||
Comment 4•3 years ago
|
||
Updated•3 years ago
|
Comment 6•3 years ago
|
||
Backed out for causing py unit test failures
Backout link: https://hg.mozilla.org/integration/autoland/rev/a505e98fa2fdc10dd9578bd5893786e803571dff
Comment 7•3 years ago
|
||
The issue is the message Failure: ModuleNotFoundError (No module named 'yaml') at https://treeherder.mozilla.org/logviewer?job_id=398502710&repo=autoland&lineNumber=915 - the other 'failure' lines are permanent and even part of successful task runs.
Comment 9•3 years ago
|
||
| bugherder | ||
Updated•3 years ago
|
Updated•3 years ago
|
Description
•