ReleaseEngineering/Archive/Enable or Disable Updates on Aurora: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "When Nightly merges into Aurora every 6 weeks we lock Aurora updates at a specific old version for a period of time (days to a week) while QA runs some tests. Once their tests...")
 
 
(26 intermediate revisions by 6 users not shown)
Line 1: Line 1:
When Nightly merges into Aurora every 6 weeks we lock Aurora updates at a specific old version for a period of time (days to a week) while QA runs some tests. Once their tests have passed, we re-enable updates. This document describes how to do both of these things.
= This page is obsolete =
 
When Nightly merges into Aurora every 6 weeks we lock Aurora updates at a specific old version for a period of time (days to a week) while QA runs some tests. Once their tests have passed, we re-enable updates. We're also occaisonly asked to disable updates temporarily for other reasons. This document describes how to do both of these things.
 
Note the magic rule ids below. These correspond to ids of rows in the "rules" table of Balrog. If we fix {{bug|1067402}} we can pass more intelligable values here.


= Disabling Updates =
= Disabling Updates =
* Change the Firefox and Fennec "aurora" channel to a specific nightly buildid in Balrog. For example, "20131019004007". Release Management should specify the buildid to use. Once you have that, do the following:
NOTE: Disabling no longer has to be done by hand during uplifts. The uplift script does it.
*# Go to [https://aus4-admin.mozilla.org/rules.html the Balrog Admin interface's rules page].
*# Find the rule that has "Fennec" for the product and "aurora" for the channel.
*# Click the "Mapping" drop down for that rule and find the "Fennec-mozilla-aurora-nightly" entry that contains the requested buildid and select it.
*# Scroll to the right and click "Update" to make the change.
*# Repeat the above instructions for Firefox.
* Adjust the upload location for new Aurora nightlies (note: this step becomes unnecessary after we stop uploading to AUS3):
*# Change aus2_base_upload_dir, aus2_base_upload_dir_l10n, aus2_mobile_base_upload_dir, and aus2_mobile_base_upload_dir_l10n to use "mozilla-aurora-test". See [https://bug856740.bugzilla.mozilla.org/attachment.cgi?id=731965 this patch for an example].
*# Reconfig the build masters for it.


= Enabling Updates =
= Enabling Updates =
* Change the Firefox and Fennec "aurora" channels back to the -latest release:
Unlike disabling, Firefox and Fennec aren't always re-enabled at the same time. Make sure you are connected to releng VPN.
*# Go to [https://aus4-admin.mozilla.org/rules.html the Balrog Admin interface's rules page].
 
*# Find the rule that has "Fennec" for the product and "aurora" for the channel.
'''NOTE''': You may not be able to run these scripts unless you have a linux laptop. See {{bug|1151633}} for details and workarounds.
*# Click the "Mapping" drop down for that rule and select "Fennec-mozilla-aurora-nightly-latest".
 
*# Scroll to the right and click "Update" to make the change.
== Fennec ==
*# Repeat the above instructions for Firefox.
<pre>
* Adjust the upload location for new Aurora nightlies (note: this step becomes unnecessary after we stop uploading to AUS3):
cd /tmp
*# Change aus2_base_upload_dir, aus2_base_upload_dir_l10n, aus2_mobile_base_upload_dir, and aus2_mobile_base_upload_dir_l10n to use "mozilla-aurora". See [https://bug856740.bugzilla.mozilla.org/attachment.cgi?id=731965 this patch for an example].
rm -rf tools
*# Reconfig the build masters for it.
hg clone https://hg.mozilla.org/build/tools
* Push the auroratest snippets to aurora (also unnecessary after we stop uploading to AUS3):
cd tools/scripts/updates
*# As ffxbld@aus3-staging:
scp cltbld@buildbot-master81.bb.releng.scl3.mozilla.com:/builds/buildbot/build_scheduler/master/BuildSlaves.py oauth.txt
rsync -av /opt/aus2/incoming/2/Firefox/mozilla-aurora{-test,}/
# Run with dry run first, sanity check the "Would've unlocked" lines.
rsync -av /opt/aus2/incoming/2/Fennec/mozilla-aurora{-test,}/
python2.7 balrog-nightly-locker.py -a https://aus4-admin.mozilla.org/api -c oauth.txt -u ffxbld -r 8 -n unlock
# Run without dry run to unlock the updates
python2.7 balrog-nightly-locker.py -a https://aus4-admin.mozilla.org/api -c oauth.txt -u ffxbld -r 8 unlock
</pre>
 
== Firefox ==
<pre>
cd /tmp
rm -rf tools
hg clone https://hg.mozilla.org/build/tools
cd tools/scripts/updates
scp cltbld@buildbot-master81.bb.releng.scl3.mozilla.com:/builds/buildbot/build_scheduler/master/BuildSlaves.py oauth.txt
# Run with dry run first, sanity check the "Would've unlocked" lines.
python2.7 balrog-nightly-locker.py -a https://aus4-admin.mozilla.org/api -c oauth.txt -u ffxbld -r 10 -n unlock
# Run without dry run to unlock the updates
python2.7 balrog-nightly-locker.py -a https://aus4-admin.mozilla.org/api -c oauth.txt -u ffxbld -r 10 unlock
</pre>
 
== Cleanup ==
<pre>
# preferably with srm or equivalent
srm oauth.txt
</pre>
 
== Update bouncer ==
When re-enable updates for Aurora, update the following bouncer locations to use the new version for aurora:
* [https://bounceradmin.mozilla.com/admin/mirror/location/?product__id__exact=2006 firefox-aurora-latest]
* [https://bounceradmin.mozilla.com/admin/mirror/location/?product__id__exact=3686 firefox-aurora-latest-ssl]
* [https://bounceradmin.mozilla.com/admin/mirror/location/?product__id__exact=3685 firefox-aurora-latest-l10n]
* [https://bounceradmin.mozilla.com/admin/mirror/location/?product__id__exact=6510 firefox-aurora-latest-l10n-ssl]
* [https://bounceradmin.mozilla.com/admin/mirror/location/?product__id__exact=2061 firefox-aurora-stub]
* [https://bounceradmin.mozilla.com/admin/mirror/location/?product__id__exact=6511 firefox-aurora-stub-l10n]
 
NB: it is expected that the two stub products have a win and win64 location which both point to the same location. We don't have a win64 stub installer, instead the mislabeled 32bit stub selects the correct full installer at runtime.

Latest revision as of 01:01, 11 July 2017

This page is obsolete

When Nightly merges into Aurora every 6 weeks we lock Aurora updates at a specific old version for a period of time (days to a week) while QA runs some tests. Once their tests have passed, we re-enable updates. We're also occaisonly asked to disable updates temporarily for other reasons. This document describes how to do both of these things.

Note the magic rule ids below. These correspond to ids of rows in the "rules" table of Balrog. If we fix bug 1067402 we can pass more intelligable values here.

Disabling Updates

NOTE: Disabling no longer has to be done by hand during uplifts. The uplift script does it.

Enabling Updates

Unlike disabling, Firefox and Fennec aren't always re-enabled at the same time. Make sure you are connected to releng VPN.

NOTE: You may not be able to run these scripts unless you have a linux laptop. See bug 1151633 for details and workarounds.

Fennec

cd /tmp
rm -rf tools
hg clone https://hg.mozilla.org/build/tools
cd tools/scripts/updates
scp cltbld@buildbot-master81.bb.releng.scl3.mozilla.com:/builds/buildbot/build_scheduler/master/BuildSlaves.py oauth.txt
# Run with dry run first, sanity check the "Would've unlocked" lines.
python2.7 balrog-nightly-locker.py -a https://aus4-admin.mozilla.org/api -c oauth.txt -u ffxbld -r 8 -n unlock
# Run without dry run to unlock the updates
python2.7 balrog-nightly-locker.py -a https://aus4-admin.mozilla.org/api -c oauth.txt -u ffxbld -r 8 unlock

Firefox

cd /tmp
rm -rf tools
hg clone https://hg.mozilla.org/build/tools
cd tools/scripts/updates
scp cltbld@buildbot-master81.bb.releng.scl3.mozilla.com:/builds/buildbot/build_scheduler/master/BuildSlaves.py oauth.txt
# Run with dry run first, sanity check the "Would've unlocked" lines.
python2.7 balrog-nightly-locker.py -a https://aus4-admin.mozilla.org/api -c oauth.txt -u ffxbld -r 10 -n unlock
# Run without dry run to unlock the updates
python2.7 balrog-nightly-locker.py -a https://aus4-admin.mozilla.org/api -c oauth.txt -u ffxbld -r 10 unlock

Cleanup

# preferably with srm or equivalent
srm oauth.txt

Update bouncer

When re-enable updates for Aurora, update the following bouncer locations to use the new version for aurora:

NB: it is expected that the two stub products have a win and win64 location which both point to the same location. We don't have a win64 stub installer, instead the mislabeled 32bit stub selects the correct full installer at runtime.

Retrieved from "https://wiki.mozilla.org/index.php?title=ReleaseEngineering/Archive/Enable_or_Disable_Updates_on_Aurora&oldid=1175426"