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

From MozillaWiki
Jump to navigation Jump to search
(obsolete header)
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Release Engineering How To|Promote_Unagi_to_beta}}
{{Release Engineering How To|Promote_Unagi_to_beta}}
<blockquote style=" border: solid thin grey; text-align: center;"><big>
This page is obsolete.</big>
</blockquote>


= Provided information =  
= Provided information =  


QA will ask us to promote a build with information like this:
QA will ask us to promote a build with information similar to below, in an email sent either to release@ or b2g-r-d@:
<pre>OK to promote Build ID: 20130510070207 to Dogfooders</pre>
<pre>Release Engineering Reference - Please PROMOTE THE FOLLOWING BUILD:
<pre>Release Engineering Reference - Please PROMOTE THE FOLLOWING BUILD:
Build updated from:
Build updated from:
·        gecko: e86df153bcab6e1b645e187c646b0c64e97bd68d
          gecko: e86df153bcab6e1b645e187c646b0c64e97bd68d
·        gaia: 21cedfd1787f4aff26721fc0f160e771db5cd67d
          gaia: 21cedfd1787f4aff26721fc0f160e771db5cd67d
·        build ID: 20130211070202
          build ID: 20130211070202
          Channel: beta
</pre>
</pre>
They will probably not tell you what branch that came from, so you need to search for ''releng-beta.py'' in [http://hg.mozilla.org/build/buildbot-configs/file/production/mozilla/b2g_config.py b2g_config.py].


Now you know the $buildID and the $branch for the following steps, substitute as necessary.
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.


= Publish update to beta channel =
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.
To make updates work properly you need to copy some files from the nightly directory to the beta directory.


Use a buildbot master as a jump host:
= Create RIL repack =
ssh -i .ssh/b2gbld_dsa ec2-user@update.boot2gecko.org
This is now a separate process step, and not part of promotion.
buildID=<your $buildID here>
cd /data/update-channels/beta
cp -avi ../nightly/b2g_update_${buildID}.mar ./b2g_beta_update_${buildID}.mar
cp -avi ../nightly/b2g_update_source_${buildID}.xml ./b2g_beta_update_${buildID}.xml
cp -avi ../nightly/application_${buildID}.ini .
* Verify that http://update.boot2gecko.org/beta/update.xml returns proper $buildID


Announce this by sending email to: b2g-release-drivers@. Sample:
Use these [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Create_B2G_RIL_Repack instructions].


Subject: [release] #buildID# is now promoted for dogfooders
= Notify partners =
=====
This is now a separate process step, and not part of promotion.
This should be available for people to see immediately.
For reference, this build used the following changesets:
gecko: <copy paste from the source.xml>
gaia: <copy paste from the source.xml>
Thanks
[RelEng human]


= Publish image file for flashing =
Use these [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Notify_Partners_of_good_b2g_build instructions].
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.


Use a buildbot master as a jump host:
= How to backout a promotion =
ssh -i .ssh/b2gbld_dsa b2gbld@stage.mozilla.org


buildID=<your $buildID here>
Sometimes we'll get a bug requesting that we revert to a previous version
branch=<your $branch here>
datestr=`echo $buildID | sed -r 's,([0-9]{4})([0-9]{2})([0-9]{2})([0-9]{2})([0-9]{2})([0-9]{2}),\1/\2/\1-\2-\3-\4-\5-\6,'`
sourcefile="/mnt/pvt_builds/pub/mozilla.org/b2g/nightly/${branch}-unagi/${datestr}/unagi.zip"


if [ ! -e $sourcefile ]; then
For instance, <s>{{bug|860783}}</s>,
  echo ERROR: $sourcefile not found, check variables
else
  cp -avi $sourcefile  \
          /mnt/netapp/stage/releases.mozilla.com/b2g-testdrivers/unagi_beta_${buildID}.zip && \
  ln -sfv unagi_beta_${buildID}.zip /mnt/netapp/stage/releases.mozilla.com/b2g-testdrivers/unagi_beta_latest.zip
fi


* Double check if you can download the files using
<pre>
* https://releases.mozilla.com/b2g-testdrivers/unagi_beta_latest.zip
buildbot master -> ssh -i .ssh/b2gbld_dsa ec2-user@update.boot2gecko.org
* https://releases.mozilla.com/b2g-testdrivers/unagi_beta_${buildID}.zip
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}}
= Create RIL repack =
we needed to move away everything newer than *2013040923* and then touch the 040923 files.
The $datestr from above is used for UNAGI_DATE in these [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Create_B2G_RIL_Repack instructions]
</pre>
 
= Notify partners =
[https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Notify_Partners_of_good_b2g_build details here]

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"