Releases/Firefox 14.0b8/BuildNotes

Notes About Releasing

Please update the Notes Template and the Release:Primer for future releases (bug fixes, changes to automation) as needed

Bugs hit

Enter any bugs pre-existing or newly discovered and filed during the release:

Build Engineers

nthomas - Tracking bug: bug 758790

Signed-off Revision(s)

Build 1: 7945471fc07f

L10N changesets

Instructions on how to get them

aki created these milestones.

Tags

Manually tag the automation code, then record the generated tags below. (details)

Build # Branch, Tags Changeset
1 MOBILE140_2012061918_RELBRANCH FENNEC_14_0b8_BUILD1 FENNEC_14_0b8_RELEASE da2c4d1100da
GECKO140_2012061918_RELBRANCH FIREFOX_14_0b8_BUILD1 FIREFOX_14_0b8_RELEASE f8d3886db65a

Build data

Firefox

Build # Type Build ID Build machine Time to build
1 Linux 20120619191901 linux-ix-slave28 1 hrs, 7 mins, 11 secs
Linux64 linux64-ix-slave21 1 hrs, 5 mins, 53 secs
Mac bld-lion-r5-052 1 hrs, 17 mins, 8 secs
Windows

Fennec

Build # Type Build ID Build machine Time to build
1 android 20120619190045 linux-ix-slave35 50 mins, 46 secs
android-xul linux-ix-slave19 49 mins, 35 secs

Notes

Build 1

Did you ship the L10n milestone ???

Yes

Set reserved slaves

  • Reserve slaves (you need ~6 each of linux, linux64, win32 (w32), and macosx64 (bld-r5-lion)). Doing this 2-3 hours in advance should speed things up. e.g.:
[cltbld@buildbot-master13 master]$ pwd
/builds/buildbot/build1/master
[cltbld@buildbot-master13 master]$ cat reserved_slaves
6

Preparing to start Automation

detailed instructions

  • aki created l10n milestones
  • didn't do a clobber as we always clobber now, and armenzg did an accidental one yesterday
  • For build1 only, create a symlink for your $version (eg 11.0b4, 10.0.2esr, 10.0.2, 3.6.27) (until bug 725839 is resolved)
# ffxbld@stage, or tbirdbld and use thunderbird in path
cd /pub/mozilla.org/firefox/nightly/
mkdir ../candidates/$version-candidates
ln -s ../candidates/$version-candidates $version-candidates
  • moved 6 mw32-ix and 6 bld-lion-r5 over to bm13
  • Updated l10n changesets for desktop, mobile
  • Double landed automation configs
  • Tag buildbot-configs, buildbotcustom, & tools with {FIREFOX,FENNEC}_14_0b8_{RELEASE,BUILD1}
  • update and reconfigure the master
  • test run the automation
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u nthomas -V 14.0b8 --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
  • no problems found so started the automation ← monitor progress on buildbot (e.g. beta)
    • the same command as above but without the "--dryrun"

E-mail Metrics

Sent

Firefox,firefox,firefox,14.0b8,14.0
Fennec,firefox-mobile,fennec,14.0b8,14.0

Tag

No problems

Bouncer Submitter

No problems

Source

No problems

Build

Firefox

Linux32/64 & Mac OK

Firefox repacks

Linux32/64 OK

Fennec

No problems

Fennec repacks

No problems

Unittests / Talos

details

  1. Look to see that they ran
  2. Document any oranges (per platform) for unittests - if possible, try to confirm it's known/random
  3. Make sure there's no red/failures that we need to have a dev look at

XULRunner

Source

No problems

Build

No problems

Push to Mirrors

No problems

Android Signing

Now run on 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

since the XUL build won't be used.

Checksums

XR OK

Updates

Update verify

NOTHING DONE BELOW HERE

Reset reserved slaves

Needs to be reset to 0, and free scl3 slaves locked to bm13.

Check permissions / AV scan

Push to internal mirrors

Final verification

Going to Beta

Run backupsnip

NOTE: Remember to do this at least 2 hours ahead of the expected "go to beta" email. details

Remember to ssh to aus3-staging using your short LDAP name and then run sudo su - ffxbld once on. If you intend to use screen, initiate your screen session while you are still yourself.

Push to beta channel

Publish Fennec to the Play Store (for beta releases and release releases)

Push the files
Play Store

IMPORTANT - Make sure to follow instructions!

  • download both multi apks. These have the same name so save them to separate directories.
  • visit https://market.android.com/publish
  • choose "Firefox Beta" or "Firefox"
  • select the "APK Files" tab and choose "Upload APK"
    • choose the android multi apk that you downloaded and hit "upload"
      • NOTE: the progress bar does not seem to show progress (at least on Google Chrome)
    • when it finishes uploading, verify VersionCode is the build date (almost anyway, the market reports an hour later than our buildID)
    • hit "Save"
  • If you're also uploading XUL Fennec, repeat the same steps for the android-xul multilocale apk
  • activate new android apk (You should see an Error message since both apk's are active)
  • deactivate old android apk (You should not see the Error message anymore). You can identify the two build types by
    • Native Fennec (phones) has Supported screens: small-large
    • XUL Fennec (tablets) has Supported screens: xlarge
  • If you're also activating XUL Fennec, repeat those steps for the android-xul multilocale apk.
  • hit "Save"
  • If this is a beta 1, go to "Product Details" tab -> Recent Changes, change the url to http://www.mozilla.com/en-US/mobile/{VERSION}beta/releasenotes/
    • and hit "Save"