ReleaseEngineering/Archive/Update B2G Blobs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Remove the how to header, add obsolete header) |
||
| Line 1: | Line 1: | ||
= This page is obsolete = | |||
* [https://wiki.mozilla.org/ReleaseEngineering:Buildduty:Other_Duties#How_to_upload_to_Tooltool Upload the file to tooltool] | * [https://wiki.mozilla.org/ReleaseEngineering:Buildduty:Other_Duties#How_to_upload_to_Tooltool Upload the file to tooltool] | ||
* Update your local clone of https://hg.mozilla.org/integration/b2g-inbound/ | * Update your local clone of https://hg.mozilla.org/integration/b2g-inbound/ | ||
Revision as of 00:59, 11 July 2017
This page is obsolete
- Upload the file to tooltool
- Update your local clone of https://hg.mozilla.org/integration/b2g-inbound/
- Edit the appropriate device config. eg. b2g/config/hamachi/releng-hamachi.tt
- Change 'size' and 'digest' of the file being updated.
- Attach a patch to the bug for review
- Once reviewed, land the patch on b2g-inbound
- Watch for a successful build, then uplift to the relevant branch(es) mentioned in the bug, specifying a=NPOTB
- As an alternative to uplifting the patch yourself, set a [checkin-needed-<branchname>] to flag the Sheriffs to do the uplift for you.
Note: the backup-helix tarball needs to be repacked such that the top level directory changes from backup-helix/ to backup-ics/ [1][2]. Use the reparent-tarball script to automate this.