ReleaseEngineering/Archive/Promote Unagi to beta: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "{{Release Engineering How To|Promote_Unagi_to_beta}} = Convert date to build ID = Since we build nightly and beta as separate builds, their build IDs may be different. You need ...")
 
(obsolete header)
 
(32 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{Release Engineering How To|Promote_Unagi_to_beta}}
{{Release Engineering How To|Promote_Unagi_to_beta}}


= Convert date to build ID =
<blockquote style=" border: solid thin grey; text-align: center;"><big>
Since we build nightly and beta as separate builds, their build IDs may be different. You need to find build ID for the beta build. For example, if release-drivers want to promote 12-12-12 build:
This page is obsolete.</big>
* go to http://update.boot2gecko.org/betatest/
</blockquote>
* search for update_20121212*.xml
* open that file and search for buildID (20121212102240 in my case)


= Publish updates =
= Provided information =  
To make updates work properly you need to copy 2 files from the betatest direcotry to the beta directory:
 
* MAR file (you also need to rename it)
QA will ask us to promote a build with information similar to below, in an email sent either to release@ or b2g-r-d@:
* application.ini file
<pre>OK to promote Build ID: 20130510070207 to Dogfooders</pre>
Use a mock based host as a jump host:
<pre>Release Engineering Reference - Please PROMOTE THE FOLLOWING BUILD:
ssh -i .ssh/b2gbld_dsa ec2-user@update.boot2gecko.org
Build updated from:
bid=20121212102240
          gecko: e86df153bcab6e1b645e187c646b0c64e97bd68d
cd /data/update-channels/beta
          gaia: 21cedfd1787f4aff26721fc0f160e771db5cd67d
cp -avi ../betatest/application_$bid.ini ../beta/
          build ID: 20130211070202
cp -avi ../betatest/b2g_update_$bid.mar ./b2g_beta_update_$bid.mar
          Channel: beta
* Double check if http://update.boot2gecko.org/beta/update.xml returns proper build ID
</pre>
= Upload image file to https://releases.mozilla.com/b2g-testdrivers/ =
 
Download https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-beta-unagi_betatest/2012/12/2012-12-12-10-22-40/unagi.zip as unagi_beta_$bid.zip
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.
Copy it to stage.m.o using one of the slaves:
 
chmod 644 unagi_beta_$bid.zip
As of 2013-03-19, RelEng uses a script to do the promotion. See [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Perform_b2g_dogfood_tasks script instructions] for details.
rsync -avP -e "ssh -i $HOME/.ssh/b2gbld_dsa" unagi_beta_$bid.zip b2gbld@stage.mozilla.org:/mnt/netapp/stage/releases.mozilla.com/b2g-testdrivers/
 
ssh -i $HOME/.ssh/b2gbld_dsa b2gbld@stage.mozilla.org ln -sf unagi_beta_$bid.zip /mnt/netapp/stage/releases.mozilla.com/b2g-testdrivers/unagi_beta_l
= Create RIL repack =
atest.zip
This is now a separate process step, and not part of promotion.
* Dowble check if you can download the files.
 
Use these [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Create_B2G_RIL_Repack instructions].
 
= Notify partners =
This is now a separate process step, and not part of promotion.
 
Use these [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Notify_Partners_of_good_b2g_build instructions].
 
= How to backout a promotion =
 
Sometimes we'll get a bug requesting that we revert to a previous version
 
For instance, <s>{{bug|860783}}</s>,
 
<pre>
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.
</pre>

Latest revision as of 00:48, 11 July 2017


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.
Retrieved from "https://wiki.mozilla.org/index.php?title=ReleaseEngineering/Archive/Promote_Unagi_to_beta&oldid=1175397"