Releases/Firefox 10.0b1/BuildNotes

From MozillaWiki
Jump to: navigation, search

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:

  • bug 712753 - release sanity dies with versions with two digits
  • bug 712830 - tm-b01-master01 is slow; busted win32 repacks
  • doesn't look like reserved slaves works...no free slaves to do win32 repacks after I triggered them

Build Engineers

catlee - Tracking bug: bug 712133

Signed-off Revision(s)

Build 1: 3e2a4142ebb9

L10N changesets

Instructions on how to get them

Tags

Build # Branch, Tags Changeset
1 MOBILE100_2011122112_RELBRANCH, FENNEC_10_0b1_RELEASE, FENNEC_10_0b1_BUILD1 3e2a4142ebb9
GECKO100_2011122113_RELBRANCH, FIREFOX_10_0b1_BUILD1, FIREFOX_10_0b1_RELEASE 3e2a4142ebb9

Build data

Firefox

Build # Type Build ID Build machine Time to build
1 Linux 20111221135037 mv-moz2-linux-ix-slave18 4 hrs, 20 mins, 46 secs
Linux64 moz2-linux64-slave06 4 hrs, 51 mins, 11 secs
Mac moz2-darwin10-slave53 4 hrs, 52 mins, 51 secs
Windows mw32-ix-slave05 4 hrs, 19 mins, 56 secs

Fennec

Build # Type Build ID Build machine Time to build
1 android 20111221133754 mv-moz2-linux-ix-slave10 2 hrs, 17 mins, 26 secs
linux mv-moz2-linux-ix-slave02 1 hrs, 4 mins, 50 secs
macosx bm-xserve16 2 hrs, 20 mins, 47 secs
win32 mw32-ix-slave03 2 hrs, 15 mins, 20 secs

Notes

Build 1

Preparing to start Automation

  • Set clobbers for the buildbot-master08 any builder any release
  • Reserve slaves
 echo 8 > /builds/buildbot/build1/master/reserved_slaves_bm08-build1
  • Update l10n changesets for desktop, mobile
  • Land automation configs (are you or buildduty going to reconfig? great, merge. otherwise double-land only your configs)
  • Tag buildbot-configs, buildbotcustom, & tools with build & release tags
  • release_sanity:
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u catlee -pfirefox,fennec -V 10.0b1 --branch mozilla-beta --build-number 1 -c release-firefox-mozilla-beta.py -c release-fennec-mozilla-beta.py --dryrun localhost:9001
Traceback (most recent call last):
  File "../tools/buildbot-helpers/release_sanity.py", line 394, in <module>
    if not verify_l10n_dashboard(releaseConfig['l10nRevisionFile']):
  File "../tools/buildbot-helpers/release_sanity.py", line 238, in verify_l10n_dashboard
    releaseConfig['productName']),
  File "/builds/buildbot/build1/tools/lib/python/release/versions.py", line 22, in getL10nDashboardVersion
    if parsed.group(1) and parsed.group(1).startswith('b'):
AttributeError: 'NoneType' object has no attribute 'group'

Landed bug 712753 and re-ran. All tests passed.

  • update and reconfigure the master
  • start automation
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u catlee -pfirefox,fennec -V 10.0b1 --branch mozilla-beta --build-number 1 -c release-firefox-mozilla-beta.py -c release-fennec-mozilla-beta.py localhost:9001
  • reconfigure other masters (or ask the buildduty person to do this) if you have done a merge (and not double-land) to production

E-mail Metrics

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

Tag

No problems

Bouncer Submitter

No problems

Source

No problems

Start autosign

NOTE: use new signcode keys from d:/2011-keys

Instructions are in CombinedSigning

Build

Firefox

No problems

Firefox repacks

win32 repacks didn't fire, most likely because of db issues at the time. kicked them off with manhole:

>> master.scheduler_manager
<buildbot.schedulers.manager.SchedulerManager instance at 0x22ce9d88>
>>> for s in list(master.scheduler_manager):
...     if s.name == 'release-mozilla-beta-win32_repack':
...         break
... 
>>> s
<buildbot.schedulers.triggerable.Triggerable instance at 0x229ffb00>
>>> s.name
'release-mozilla-beta-win32_repack'
>>> builder = status.getBuilder('release-mozilla-beta-win32_build')
>>> build = builder.getBuild(77)
>>> ss = build.getSourceStamp()
>>> build.getProperty('got_revision')
'c130e43aa4b5'
>>> ss = ss.getAbsoluteSourceStamp('c130e43aa4b5')
>>> ss.branch
u'releases/mozilla-beta'
>>> ss.changes[0].properties
{'products': 'firefox,fennec', 'script_repo_revision': 'FIREFOX_10_0b1_RELEASE'}
>>> from buildbot.process.properties import Properties
>>> props_to_set = Properties()
>>> for p in 'buildid', 'builduid':
...     props_to_set.setProperty(p, build.getProperty(p), "%s (in triggering build)" % build.getProperties().getPropertySource(p))
... 
>>> props_to_set
{'buildid': '20111221135037', 'builduid': u'2cad05cf7f4f442e966f6a285c88bdda'}
>>> props_to_set.asList()
[('buildid', '20111221135037', 'SetProperty Step (in triggering build)'), ('builduid', u'2cad05cf7f4f442e966f6a285c88bdda', u'buildUIDSchedFunc (in triggering build)')]
>>> s.trigger(ss, set_props=props_to_set)
<Deferred #0>

linux repacks suffered the same problem; fixed similarly

Fennec

Android

No problems

Desktop Builds

No problems

Mobile Desktop repacks

No problems

Unittests / Talos

  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

No problems

Source

No problems

Build

No problems

Signing

NOTE: use new signcode keys from d:/2011-keys NOT DONE YET

Firefox Signing

No issues

Android Signing

Instructions in [MobileSigning https://intranet.mozilla.org/Build:MobileSigning]

I messed up the passphrases again, caught by signature verification

Android Signature Verification

Caught my bad passphrase entry

L10N verify

No problems

Updates

No problems...just slow

Update verify

Major Update

Update verify

No problems

Socorro Product Data Updates

Reset reserved slaves

Done

Run backupsnip

Done

Check permissions / AV scan

Done

Push files to internal mirrors

Mirrors Policy Done

Final verification

Push to beta

# cltbld@aus2-staging
~/bin/pushsnip Firefox-10.0b1-build1

Publish Fennec to the Android Market

Push the files

  • edit push_fennec_{beta,release}.sh as ffxbld@stage
  • run push_fennec_{beta,release}

Android Market

IMPORTANT - Make sure to follow instructions!

  • download multi apk (e.g. multi/fennec-8.0b4.multi.eabi-arm.apk)
  • visit https://market.android.com/publish
  • choose "Firefox Beta" or "Firefox"
  • select the "APK Files" tab and choose "Upload APK"
    • choose the 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 build date
    • hit "Save"
  • activate new apk (You should see an Error message since both apk's are active)
  • deactivate old apk (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"

Push XULRunner to Mirrors

Update XULRunner wiki page

Update symlinks

Once we're signed off on the release channel.

Remove index.html files

If you created them earlier to hide the release.