Releases/Firefox 15.0b1/BuildNotes

From MozillaWiki
Jump to: navigation, search

Checklist

Notes

Build 1

Created and shipped the l10n milestone

I got a zeus "Service unavailable" page the first time I tried to do this. I went through everything again and it worked fine (albeit slowly).

  • Clicked "ship" for Firefox
  • Downloaded l10n changesets
  • Clicked "ship it"
  • Clicked "ship" for Fennec
  • Clicked "add"
  • Filled out form:
    • repo: releases/mozilla-beta
    • branch: default
    • path: mobile/android/locales/maemo-locales
  • Clicked "Generate it"
  • Downloaded l10n changesets
  • Clicked "Ship it"

Set reserved_slaves

As cltbld@buildbot-master13:

echo 10 > /builds/buildbot/build1/master/reserved_slaves

Verified that we had enough slaves available

Had to lock 6 mw32-ix slaves to bm13 for repacks, all other platforms had at least 5 slaves.

Started the Automation

  • Created the candidates directory + symlink:
# ffxbld@stage
version=15.0b1
product=firefox
cd /pub/mozilla.org/$product/nightly/
mkdir ../candidates/$version-candidates
ln -s ../candidates/$version-candidates $version-candidates
  • Landed configuration file updates
  • Transplanted http://hg.mozilla.org/build/buildbotcustom/rev/32ccb8ddeef1 to the production-0.8 branch, at Rail's request.
  • Tagged the tip of of buildbot-configs' production branch, tip of buildbotcustom's production-0.8 branch, and tools' default branch with {FIREFOX,FENNEC}_15_0b1_{RELEASE,BUILD1}
  • Updated & reconfiged buildbot-master13
  • Ran release sanity in dryrun mode:
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum \
    -V 15.0b1 --branch mozilla-beta --build-number 1 \
    --release-config release-firefox-mozilla-beta.py \
    --release-config release-fennec-mozilla-beta.py --products firefox,fennec  \
    --dryrun localhost:9001
  • Got errors regarding mozconfigs:
WARNING : if test "$IS_NIGHTLY" != ""; then not in win32 ['ac_add_options --enable-update-channel=nightly', 'ac_add_options --enable-signmar', 'ac_add_options --enable-js-diagnostics', '. $topsrcdir/configs/mozilla2/win32/include/choose-make-flags', 'mk_add_options MOZ_MAKE_FLAGS=-j1']!
ERROR : found in browser/config/mozconfigs/win32/nightly but not in browser/config/mozconfigs/win32/release: if test "$IS_NIGHTLY" != ""; then
WARNING : ac_add_options --disable-auto-deps not in win32 ['ac_add_options --enable-update-channel=nightly', 'ac_add_options --enable-signmar', 'ac_add_options --enable-js-diagnostics', '. $topsrcdir/configs/mozilla2/win32/include/choose-make-flags', 'mk_add_options MOZ_MAKE_FLAGS=-j1']!
ERROR : found in browser/config/mozconfigs/win32/nightly but not in browser/config/mozconfigs/win32/release: ac_add_options --disable-auto-deps
WARNING : fi not in win32 ['ac_add_options --enable-update-channel=nightly', 'ac_add_options --enable-signmar', 'ac_add_options --enable-js-diagnostics', '. $topsrcdir/configs/mozilla2/win32/include/choose-make-flags', 'mk_add_options MOZ_MAKE_FLAGS=-j1']!
ERROR : found in browser/config/mozconfigs/win32/nightly but not in browser/config/mozconfigs/win32/release: fi
ERROR : Error verifying mozconfigs
    • Did a manual diff of the win32 nightly vs. release mozconfig, relevant sections are:
-if test "$IS_NIGHTLY" != ""; then 
-  ac_add_options --disable-auto-deps
-fi
    • This means that we need to add those lines to the whitelist or otherwise cope with difference. OK to ignore this, though. FILEME.
  • And about a missing locale:
2012-07-17 10:07:27,537 : ERROR : cannot find l10n locale lg in repo https://hg.mozilla.org/releases/l10n/mozilla-beta/lg/file/f3caa9bc805b
    • Pinged release-drivers about this, Axel fixed it up. Reran release sanity and only had the mozconfig issue
  • Ran release sanity with --bypass-check to force it to start:
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum \
    -V 15.0b1 --branch mozilla-beta --build-number 1 \
    --release-config release-firefox-mozilla-beta.py \
    --release-config release-fennec-mozilla-beta.py --products firefox,fennec  \
    --bypass-check localhost:9001

Email Metrics

Sent the following mail to metrics-alerts@mozilla.org:

Firefox,firefox,firefox,15.0b1,15.0
Fennec,firefox-mobile,fennec,15.0b1,15.0

Create XULRunner candidates directory

Initial XULRunner builds & source failed out when uploading. This was because bug 725839 got us uploading to /pub/mozilla.org/xulrunner/candidates, and that directory didn't exist. Filed & fixed in bug 774793.

Reset reserved slaves

After update verify finished:

# cltbld@buildbot-master13
echo 0 > /builds/buildbot/build1/master/reserved_slaves 

ANDROID RESPIN DECLARED

Because of bug 774789

Push to beta channel

As ffxbld@aus3-staging

cd /opt/aus2/snippets/staging
~/bin/pushsnip Firefox-15.0b1-build1

Build 2 (Android only)

Starting the Automation

  • Landed configuration file updates to default + production branches of buildbot-configs.
  • Retagged buildbot-configs with FENNEC_15_0b1_{RELEASE,BUILD2}
  • Updated and reconfiged the master
  • Ran release sanity in dryrun mode:
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum \
    -V 15.0b1 --branch mozilla-beta --build-number 2 \
    --release-config release-fennec-mozilla-beta.py --products fennec  \
    --dryrun localhost:9001
  • Full pass, so ran it without --dryrun to start the release:
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum \
    -V 15.0b1 --branch mozilla-beta --build-number 2 \
    --release-config release-fennec-mozilla-beta.py --products fennec  \
    localhost:9001

Sign Android Build

As cltsign@signing1:

cd ~/signing-work/mozharness
hg pull -u && hg up -C
python2.6 ~/signing-work/mozharness/scripts/sign_android.py --config-file signing/android_mozilla-beta.py --platform android

Sent "Signed Android build available" mail to release-drivers@mozilla.org.

Publish Fennec

As part of this release we decided to upload the APK to the store early in order to test bug 770677's theory that doing so would reduce wait time between activation & it showing up for users. This part was done a few hours in advance of publishing:

Later, after getting the go to push live, activated the APK through:

  • Clicked "activate" for new APK
  • Clicked "deactivate" for the previous one
  • Clicked "Save"

Bugs Hit

  • bug 774714 - l10n.mozilla.org is returning 500 errors when i try to ship a milestone
  • bug 763903 - regularly run mozconfig comparison logic
  • bug 774787 - update mozilla-beta mozconfig comparisons
  • bug 774793 - create candidates directory for xulrunner