Closed Bug 631319 Opened 10 years ago Closed 9 years ago

Major updates only need to download checksums


(Release Engineering :: Release Automation: Other, defect, P5)



(Not tracked)



(Reporter: catlee, Unassigned)



(Whiteboard: [automation][optimization][major-update])

Could have sworn I filed this before, but I can't find it, so here we go (again?)

To generate major update snippets, all we need to know is the SHA512 and the file size of the target mars.  Instead of downloading all the target mars to calculate this, we could examine the .checksum files that are being generated as part of bug 578393 which contain both the SHA512 and the file size of the complete mar.
Note that the current signing procedure doesn't recreate *.checksums files for signed files.
Assignee: nobody → astoica
Assignee: astoica → catlee
Assignee: catlee → nobody
No longer blocks: hg-automation
Mass move of bugs to Release Automation component.
Component: Release Engineering → Release Engineering: Automation (Release Automation)
No longer blocks: hg-automation
We have code that would make this easy, but it only exists on a newer version of the UPDATE_PACKAGING tag than we use for MUs. Given that 3.6 is the last place we do them, and we don't do them very often right now, and also that when Balrog is in production this won't be relevant - I'm WONTFIXing this.
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: → Release Engineering
You need to log in before you can comment on or make changes to this bug.