ReleaseEngineering/Archive/Promote Unagi to beta
From MozillaWiki
< ReleaseEngineering(Redirected from ReleaseEngineering/How To/Promote Unagi to beta)
This page is obsolete.
Provided information
QA will ask us to promote a build with information similar to below, in an email sent either to release@ or b2g-r-d@:
OK to promote Build ID: 20130510070207 to Dogfooders
Release Engineering Reference - Please PROMOTE THE FOLLOWING BUILD: Build updated from: gecko: e86df153bcab6e1b645e187c646b0c64e97bd68d gaia: 21cedfd1787f4aff26721fc0f160e771db5cd67d build ID: 20130211070202 Channel: beta
Double check that the build id specified matches the "updated from" (if provided). If they differ, use the "updated from" build id (safe as it's older), and reply to the request stating that.
As of 2013-03-19, RelEng uses a script to do the promotion. See script instructions for details.
Create RIL repack
This is now a separate process step, and not part of promotion.
Use these instructions.
Notify partners
This is now a separate process step, and not part of promotion.
Use these instructions.
How to backout a promotion
Sometimes we'll get a bug requesting that we revert to a previous version
For instance, bug 860783,
buildbot master -> ssh -i .ssh/b2gbld_dsa ec2-user@update.boot2gecko.org cd /data/update-channels/nightly/ Move away the files they request you to and touch the files you want to revert to. For example, for {{bug|860783}} we needed to move away everything newer than *2013040923* and then touch the 040923 files.