Closed
Bug 1160380
(beetmover)
Opened 9 years ago
Closed 8 years ago
S3 bit mover
Categories
(Release Engineering :: Release Automation: Other, defect)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: jlund)
References
Details
Create a job which moves files from the TaskCluster artifact store to a candidates bucket in S3, applying pretty names and paths if necessary, and performing an antivirus scan. Run this after each job that produces bits, e.g. en-US builds, l10n repacks, partial update generation. Investigate security models which limit write access to only the bit mover, and only to the current 'release'. Implement bucket versioning and logging to provide history for audit.
Comment 1•9 years ago
|
||
We can also perform virus scanning as a part of this job.
See Also: → 1154282
Reporter | ||
Comment 2•9 years ago
|
||
:rail, I think you've been working on this for funsize, is that work more generally too ?
Flags: needinfo?(rail)
Comment 3•9 years ago
|
||
The work is not generic, it's very limited to funsize (not flexible at all). The code is very small and can be replaced by something more generic in the future. I just didn't want to be blocked on something generic.
Flags: needinfo?(rail)
Updated•9 years ago
|
Alias: beetmover
Comment 4•9 years ago
|
||
From my talk with Rail about secrets yesterday, if we could find a way to transmit a signed S3 PUT URL to this task, securely, that would be cool.
Reporter | ||
Comment 5•9 years ago
|
||
Not working on release promotion at the moment, releasing the bug.
Assignee: nthomas → nobody
Status: ASSIGNED → NEW
Comment 6•9 years ago
|
||
Whiteboards from Toronto sessions: https://www.dropbox.com/s/ss8hag48ip0pll1/2015-11-17%2010.42.31.jpg?dl=0 https://www.dropbox.com/s/q040m3qpo0wshu7/2015-11-17%2010.56.36.jpg?dl=0 https://www.dropbox.com/s/iab35dnewx23e8k/2015-11-17%2011.27.44.jpg?dl=0
Assignee | ||
Comment 8•8 years ago
|
||
I think we are all done here for now..
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•