Releases/Fennec 14.0b2/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 130: Line 130:
=== IF CODE HAS CHANGED ===
=== IF CODE HAS CHANGED ===


* Land 13.0b2 [http://hg.mozilla.org/build/buildbot-configs/rev/# configs] : increment the build number.
* Landed 13.0b2 configs: [http://hg.mozilla.org/build/buildbot-configs/rev/02c3e6eae112 default] [http://hg.mozilla.org/build/buildbot-configs/rev/85dc1088a3ae production]. incremented the build number to 3.
* Create a build#-spin# directory on stage, and softlink the build# to it.
* Created a build3-spin1 directory on stage, and softlinked build3 to it.
** The build# will increment, and this will be a spin 1.
** For build3-spin1:


<pre>
<pre>
Line 142: Line 140:
</pre>
</pre>


* Tag buildbot-configs, buildbotcustom, & tools with build & release tags.  
* Tagged buildbot-configs, buildbotcustom, & tools with build & release tags.  
  hg tag -f FENNEC_13_0b2_{RELEASE,BUILD#}
  hg tag -f FENNEC_13_0b2_{RELEASE,BUILD#}
* update and reconfigure the master
* update and reconfigure the master

Revision as of 00:34, 16 May 2012

Notes About Releasing

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

You will need to build a 14.0bX build using the fennec mozilla-aurora config files, then a respin of the 13.0b2 build2 android-xul build for tablets. Both will go to the market.

Bugs hit

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

Build Engineers

{aki} - Tracking bug: bug 755486

Signed-off Revision(s)

L10N changesets

  • 14.0bN will get Aurora changesets from this dashboard link. This link will change over time, so won't be useful for verifying later, but isn't dependent on a milestone being created per beta.
  • 13.0b2 build# spin# will have an empty l10n-changesets_mobile-beta.json

Tags

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

Build # Branch, Tags Changeset
1 MOBILE140_2012051517_RELBRANCH, FENNEC_14_0b2_RELEASE, FENNEC_14_0b2_BUILD1 9ff2584b47a5
13.0b2 build3 spin1 MOBILE130_2012050119_RELBRANCH FENNEC_13_0b2_BUILD3 FENNEC_13_0b2_RELEASE #

Build data

Fennec

Build # Type Build ID Build machine Time to build
1 android
android-xul
13.0b2 build # spin # android-xul

Notes

Build 1

Preparing to start Automation

detailed instructions

  • Set clobbers for mozilla-aurora
  • Reserved 5 slaves on bm12
  • Updated l10n changesets for mobile (see above) -- no changes
  • Landed configs
  • Tag buildbot-configs, buildbotcustom, & tools with build & release tags.
hg tag -f FENNEC_14_0b2_{RELEASE,BUILD1}
  • updated and reconfigured the master
  • release-sanity
# For 14.0b2 build 1:
# cltbld@bm12
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u aki -V 14.0b2 --branch mozilla-aurora --build-number 1 -c release-fennec-mozilla-aurora.py -m -l --products fennec --dryrun localhost:9001 2>&1 | tee aki.out
  • start automation ← monitor progress on buildbot (e.g. aurora)
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u aki -V 14.0b2 --branch mozilla-aurora --build-number 1 -c release-fennec-mozilla-aurora.py -m -l --products fennec localhost:9001 2>&1 | tee aki2.out

E-mail Metrics

Use the address "metrics-alerts < AT > mozilla < PERIOD > org"

# For 14.0b2 :
Fennec,firefox-mobile,fennec,14.0b2,14.0

Tag

Source

Build

Fennec

Fennec repacks

Android Signing

# cltsign@signing1
cd signing-work
hg --cwd mozharness pull
hg --cwd mozharness up -C -r default
# This will throw a number of errors until Aki fixes {{bug|750976}}.
# Verify that we error out on single locales for android-xul only.
python26 mozharness/scripts/sign_android.py --config-file signing/android_mozilla-aurora.py

Reset reserved slaves

13.0b2 build 3 spin 1

Preparing to start Automation

detailed instructions

  • Set clobbers for mozilla-beta
  • Reserved slaves on bm13
  • L10n changesets for 13.0b2 build3 spin1 will remain empty {}
  • There are code changes!

IF NO CODE HAS CHANGED

n/a, code has changed.

IF CODE HAS CHANGED

  • Landed 13.0b2 configs: default production. incremented the build number to 3.
  • Created a build3-spin1 directory on stage, and softlinked build3 to it.
# ffxbld@stage
cd /pub/mozilla.org/mobile/candidates/13.0b2-candidates
mkdir build3-spin1
ln -s build3-spin1 build3
  • Tagged buildbot-configs, buildbotcustom, & tools with build & release tags.
hg tag -f FENNEC_13_0b2_{RELEASE,BUILD#}
  • update and reconfigure the master
  • release-sanity
# For 13.0b2 build 3:
# cltbld@bm13
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u aki -V 13.0b2 --branch mozilla-beta --build-number 3 -c release-fennec-mozilla-beta.py -m -l --products fennec --dryrun localhost:9001 2>&1 | tee aki.out
  • start automation ← monitor progress on buildbot (e.g. beta)
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u aki -V 13.0b2 --branch mozilla-beta --build-number 3 -c release-fennec-mozilla-beta.py -m -l --products fennec localhost:9001 2>&1 | tee aki2.out

Tagging

(only runs if code has changed)

Source

(only runs if code has changed)

Build

Fennec

Android Signing

# cltsign@signing1
cd signing-work
hg --cwd mozharness pull
hg --cwd mozharness up -C -r default
python26 mozharness/scripts/sign_android.py --config-file signing/android_mozilla-beta.py

Release Day

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

Push the files (for beta releases and release releases)
Play Store (for beta releases and release releases)

IMPORTANT - Make sure to follow instructions!

The 14.0b2 build *must* be uploaded before the 13.0b2 build!

  • download 14.0b2 and 13.0b2 multi apk (e.g. [1] and [2])
  • visit https://market.android.com/publish
  • choose "Firefox Beta" or "Firefox"
  • select the "APK Files" tab and choose "Upload APK"
    • choose the 14.0b2 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"
  • Repeat with the 13.0b2 multi apk
  • activate new 14.0b2 and 13.0b2 apks (You should see an Error message since both apk's are active)
  • deactivate old apks (You should not see the Error message anymore)
  • 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"