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

From MozillaWiki
Jump to navigation Jump to search
(obsolete header)
 
(15 intermediate revisions by 5 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)


Note that we do two 'nightlies' a day, so the initial request has to be precise enough to distinguish which to use.
= Provided information =


= Publish updates =
QA will ask us to promote a build with information similar to below, in an email sent either to release@ or b2g-r-d@:
To make updates work properly you need to copy 2 files from the betatest direcotry to the beta directory:
<pre>OK to promote Build ID: 20130510070207 to Dogfooders</pre>
* MAR file (you also need to rename it)
<pre>Release Engineering Reference - Please PROMOTE THE FOLLOWING BUILD:
* application.ini file
Build updated from:
Use a buildbot master as a jump host:
          gecko: e86df153bcab6e1b645e187c646b0c64e97bd68d
ssh -i .ssh/b2gbld_dsa ec2-user@update.boot2gecko.org
          gaia: 21cedfd1787f4aff26721fc0f160e771db5cd67d
bid=20121212102240
          build ID: 20130211070202
cd /data/update-channels/beta
          Channel: beta
cp -avi ../betatest/b2g_update_$bid.mar ./b2g_beta_update_$bid.mar
</pre>
cp -avi ../betatest/b2g_update_source_$bid.xml ./b2g_beta_update_$bid.xml
cp -avi ../betatest/application_$bid.ini .
* Double check if http://update.boot2gecko.org/beta/update.xml returns proper build ID


= Upload image file for flashing =
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.
The [https://etherpad.mozilla.org/b2g-testdrivers-flashing flashing doc] points to https://releases.mozilla.com/b2g-testdrivers/unagi_beta_latest.zip, so we need to update that too.


First you need to identify the unagi.zip file corresponding to the update pushed.
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.
* If you are given an URL to publish like <tt>https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-b2g18-unagi/2013/01/2013-01-04-07-02-03/</tt> then you should be able to substitute <tt>mozilla-b2g18-unagi_betatest</tt> for <tt>mozilla-b2g18-unagi</tt>. If you get a 404 from the ftp server it means the buildIDs are different, skip to the next point
* Otherwise use the buildID you figured out above to locate the beta channel build at <tt>https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-b2g18-unagi_betatest/YYYY/MM/YYYY-MM-DD-HH-mm-ss/</tt>. Use the buildID you had earlier to substitute the YYYY, MM etc (eg 20130104070203 becomes 2013/01/2013-01-04-07-02-03).  


'''The key thing is to make sure that the sources.xml files matche for the nightly build which QA signed off on, and the build you are publishing'''. A diff of the two files is good way to do that.
= Create RIL repack =
This is now a separate process step, and not part of promotion.


From that directory download the unagi.zip as unagi_beta_$bid.zip
Use these [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Create_B2G_RIL_Repack instructions].


Copy it to stage.m.o using one of the masters:
= Notify partners =
set +o history
This is now a separate process step, and not part of promotion.
#bid=BUILDID
#DATESTR=YYYY/MM/YYYY-MM-DD-HH-mm-ss
#USERNAME=foo@mozilla.com
#PASSWD="PASSWD"
wget --http-user="$USERNAME" --http-password="$PASSWD" \
  -O "unagi_beta_$bid.zip" \
  https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-b2g18-unagi_betatest/$DATESTR/unagi.zip
chmod 644 unagi_beta_$bid.zip
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_latest.zip
# do the double check? requires manual password entry:
curl -I --user $USERNAME https://releases.mozilla.com/b2g-testdrivers/unagi_beta_latest.zip
curl -I --user $USERNAME https://releases.mozilla.com/b2g-testdrivers/unagi_beta_$bid.zip


* Double check if you can download the files using
Use these [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Notify_Partners_of_good_b2g_build instructions].
* https://releases.mozilla.com/b2g-testdrivers/unagi_beta_latest.zip
* https://releases.mozilla.com/b2g-testdrivers/unagi_beta_$bid.zip


= Create RIL repack =
= How to backout a promotion =
 
Sometimes we'll get a bug requesting that we revert to a previous version


[https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Create_B2G_RIL_Repack instructions]
For instance, <s>{{bug|860783}}</s>,


= Notify partners =
<pre>
[https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Notify_Partners_of_good_b2g_build details here]
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"