Releases/Firefox 4.0b3/BuildNotes

note re: bug 582700. If Windows 2000 is still busted in 4.0b3 we should set updateType=major in windows snippets. Per Rob Strong's comment it should NOT prompt despite being a MU.. Windows 2000 support was restored for 4.0b3, nothing to worry about now.

Build Engineers

armenzg, aki - tracking bug

Signed-off Revision(s)

• Build1: 2f187db8f5f6
• Build2: 69f2d0457750

Tags

On mozilla-central:

Build #	Tag	Changeset
1	GECKO20b3_20100804_RELBRANCH	2f187db8f5f6
	FIREFOX_4_0b3_BUILD1, FIREFOX_4_0b3_RELEASE	1fdcff2dbfdf
2	FIREFOX_4_0b3_BUILD2, FIREFOX_4_0b3_RELEASE	[1]

Build data

Build #	Type	Build ID	Build machine
1	[Linux compressed]	20100804111201	mv-moz2-linux-ix-slave22
2	[Windows installer/zip]	20100804193205	mw32-ix-slave05
	[Mac dmg]	20100804182810	bm-xserve15
	[Mac64 dmg]	20100804183435	moz2-darwin10-slave07
	[Linux compressed]	20100804182707	mv-moz2-linux-ix-slave22
	[Linux64 compressed]	20100804183236	moz2-linux64-slave03

Notes

Done on pm. Had to be restarted, because the master had 2 pending tag jobs.

Build 1

• Marked all builders for all releases on pm for a clobber (done by nthomas)

• Moved the following slaves to pm:
  • from pm03:
    • mv-moz2-linux-ix-slave22
    • mv-moz2-linux-ix-slave23
    • mw32-ix-slave05
    • mw32-ix-slave13
  • from pm01:
    • mv-moz2-linux-ix-slave20
    • mv-moz2-linux-ix-slave11
    • mw32-ix-slave02
    • mw32-ix-slave19
    • bm-xserve06
    • bm-xserve11
    • bm-xserve12
    • bm-xserve15

• Confirmed beta 3 l10n changesets
• Downloaded l10n-changesets from here
  • I only found the URL because Rail had mentioned previously. Axel filed bug 565640 to make it more discoverable
• Landed changes
• Reconfigured pm
• sendchange to get things running:

buildbot sendchange --username=armenzg --master=localhost:9010 --branch=mozilla-central -m "Firefox 4.0b3 build1" Go

Tag

mv-moz2-linux-ix-slave11: No problems

• Landed version bump

• Full stop at 12:11pm PDT
• only Linux had finished and had to stop the repackages for it

Build 2

• Removed *pyc and waiting
• Clobbered the release builders (NOTE: do not be connected to Build-VPN)
• Got the l10n-changesets from here
• Landed configs and l10n-changesets
• Stopped pm after checkconfig took too long
• Restarted pm after a successful checkconfig
• Sendchange:

buildbot sendchange --username=aki --master=localhost:9010 --branch=mozilla-central -m "Firefox 4.0b3 build2" go

Tag

mv-moz2-linux-ix-slave11

• Closed m-c.
• Kept hitting "abort: destination 'be' already exists" in clone_be. The step didn't actually clobber the tag directory; I had to go back and clobber all release builders on pm in clobberer before it would work (nthomas says it was requesting branch=nothing)
  • TODO aki could you elaborate on this and if there is a bug for this?
• This meant I did 3 sendchanges to get over the 2 failed tag steps. Luckily it went smoothly after that.
• Re-opened m-c.
• I tagged buildbot-configs, but ran into bug 584574 and decided to hold off on tagging buildbotcustom.
• Once bug 584574 was fixed, tagged buildbotcustom.

Source

mv-moz2-linux-ix-slave11 - no problems

Build/Repack

Some L10N repacks failed due to bug 584620 (linux64 and macosx64).

Clobbered and forced l10n repacks for the failed locales/platforms (see instructions:

# cltbld@pm
PYTHONPATH=/tools/buildbotcustom:$PYTHONPATH python force_release_l10n.py -m http://localhost:8010 -t FIREFOX_4_0b3_RELEASE -v -s locales-file -n rail@mozilla.com

locales-file content:

it linux64
es-ES linux64
ru linux64
is linux64
de linux64
pt-PT linux64
nn-NO linux64
uk macosx64
pl macosx64
sv-SE macosx64
nn-NO macosx64
zh-TW macosx64

nn-NO on linux64 never got triggered because the "nn-NO macosx64" line overwrote it. bhearsum landed a fix so this can't happen again

Unit tests

• There has been a switch over to scheduler db last night and the sendchanges are probably being sent to the wrong place. I am going to trigger them.
• TODO put link to filed bug

NOTE: I send the sendchanges to production-master01.build.mozilla.org:9009 and I changed the branch name for each sendchange to "release-$branch-$platform-opt-unittest' instead of '$branch-release-$platform-opt-unittest' NOTE2: Note the white spaces on Mac's filenames and that I had to add an apostrophe. You will see mac unit tests red because for missing them.

buildbot sendchange --master production-master01.build.mozilla.org:9009 --username sendchange-unittest --branch release-mozilla-central-linux-opt-unittest --revision 69f2d0457750 http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b3-candidates/build2/linux-i686/en-US/firefox-4.0b3.tar.bz2 http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b3-candidates/build2/linux-i686/en-US/firefox-4.0b3.tests.zip
buildbot sendchange --master production-master01.build.mozilla.org:9009 --username sendchange-unittest --branch release-mozilla-central-linux64-opt-unittest --revision 69f2d0457750 http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b3-candidates/build2/linux-x86_64/en-US/firefox-4.0b3.tar.bz2 http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b3-candidates/build2/linux-x86_64/en-US/firefox-4.0b3.tests.zip
buildbot sendchange --master production-master01.build.mozilla.org:9009 --username sendchange-unittest --branch release-mozilla-central-win32-opt-unittest --revision 69f2d0457750 http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b3-candidates/build2/unsigned/win32/en-US/firefox-4.0b3.zip http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b3-candidates/build2/unsigned/win32/en-US/firefox-4.0b3.tests.zip
buildbot sendchange --master production-master01.build.mozilla.org:9009 --username sendchange-unittest --branch release-mozilla-central-macosx-opt-unittest --revision 69f2d0457750 'http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b3-candidates/build2/mac/en-US/Firefox 4.0 Beta 3.dmg' 'http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b3-candidates/build2/mac/en-US/Firefox 4.0 Beta 3.tests.zip'
buildbot sendchange --master production-master01.build.mozilla.org:9009 --username sendchange-unittest --branch release-mozilla-central-macosx64-opt-unittest --revision 69f2d0457750 'http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b3-candidates/build2/mac64/en-US/Firefox 4.0 Beta 3.dmg' 'http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b3-candidates/build2/mac64/en-US/Firefox 4.0 Beta 3.tests.zip'

• TODO send the talos sendchanges

Sign

Using instructions.

en-US.xpi removed from stage:

#ffxbld@stage
cd /pub/mozilla.org/firefox/nightly/4.0b3-candidates/build2
rm en-US.xpi

Run usual signing script:

#!/bin/bash
set -x
set -e

PRODUCT=firefox
VERSION=4.0b3
BUILD=2
TAG=FIREFOX_4_0b3_RELEASE
REPO="mozilla-central"
EMAIL=armenzg@mozilla.com
KEYDIR=d:/2009-keys

cd ~/hg-tools
hg pull && hg up -r ${TAG}
mkdir -p ~/signing-work/${PRODUCT}-${VERSION}
cd ~/signing-work/${PRODUCT}-${VERSION}
cp ~/hg-tools/release/signing/* .

make PRODUCT=${PRODUCT} VERSION=${VERSION} \
  BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL} \
  KEYDIR=${KEYDIR} USE_NEW=1

Inspected stdout, signing log. They looked good. Ran the following:

make postsign PRODUCT=${PRODUCT} VERSION=${VERSION} \
   BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL}

Update Bouncer

bug 571869 is fixed, try to use bouncer_submitter builder to add bouncer entries and VERIFY the bug.