Releases/Firefox 3.6.3/BuildNotes

Build Engineers

bhearsum

Tags

On releases/mozilla-1.9.2:

Build #	Tag	Changeset
1

Build data

Build #	Type	Build ID	Build machine
1	Linux
	Mac
	Windows

Notes

Build 1

• Clobbered 'mozilla-1.9.2' on pm02 with clobberer.
• landed backout of changes to l10n-changesets_mozilla-1.9.2 since 3.6.2.
• Landed automation config
• Reconfiged pm02
• Started the automation:

buildbot sendchange --username=bhearsum --master=localhost:9010 --branch=releases/mozilla-1.9.2 -m "Firefox 3.6.3 build1" Go

• Manually tagged configs, buildbotcustom, and tools with FIREFOX_3_6_3_BUILD1 and FIREFOX_3_6_3_RELEASE.

Tag

No problems.

Source

No problems

HALT. Had to restart after this because tagging was done improperly (baseTag was still set to FIREFOX_3_6_2, which made us move the 3.6.2 tags rather than create 3.6.3 ones).]

Build 1 (redux)

Don't need to do a build2 since the build1 tags were never created. Cleanup from the screwup:

• Set clobberer to clobber mozilla-1.9.2 on pm02 again
• Deleted 3.6.3-candidates from stage (only had source tarball/bundle in it)
• Reverted tag commits on mozilla-1.9.2 repo:

hg up -C GECKO1922_20100315_RELBRANCH
hg tag -f -r f14062c981ba -m "Revert accidental movement of FIREFOX_3_6_2_RELEASE tag." FIREFOX_3_6_2_RELEASE
hg tag -f -r f14062c981ba -m "Revert accidental movement of FIREFOX_3_6_2_BUILD1 tag." FIREFOX_3_6_2_BUILD1
hg push ssh://hg.mozilla.org/releases/mozilla-1.9.2

• Landed fixed config
• Reconfiged pm02
• Started automation:

buildbot sendchange --username=bhearsum --master=localhost:9010 --branch=releases/mozilla-1.9.2 -m "Firefox 3.6.3 build1" Go

Tag

No problems. The tag ended up on http://hg.mozilla.org/releases/mozilla-1.9.2/rev/28ef231a65a3 instead of http://hg.mozilla.org/releases/mozilla-1.9.2/rev/d6e028dc1b68, but that makes no difference as far as the builds are concerned.

Source

Dep scheduler didn't fire. No problems

Build/Repack

Dep scheduler didn't fire. Forced builds manually until fast slaves (ix/xserve) were building, then killed the other ones (per release-drivers request).
Forced l10n builds with helper scripts:

python force_release_l10n.py -m http://production-master02.build.mozilla.org:8010 -t FIREFOX_3_6_3_RELEASE -v -b releases/mozilla-1.9.2 -p macosx -n bhearsum
python force_release_l10n.py -m http://production-master02.build.mozilla.org:8010 -t FIREFOX_3_6_3_RELEASE -v -b releases/mozilla-1.9.2 -p linux -n bhearsum
python force_release_l10n.py -m http://production-master02.build.mozilla.org:8010 -t FIREFOX_3_6_3_RELEASE -v -b releases/mozilla-1.9.2 -p win32 -n bhearsum

• Mac: no en-US problems, no l10n problems
• Linux: no en-US build problems, very slow uploads, no l10n problems
• Win32: same as Linux

Deleted en-US.xpi from stage.

Unit tests

• Mac: PASS
• Win32: PASS
• Linux: first run of mochitest-browser-chrome was orange, with an intermittent failure. Next run was green.

Sign

Started downloading builds early to speed up end to end time. Signing happened like this:

export PRODUCT=firefox
export VERSION=3.6.3
export BUILD=1
export TAG=FIREFOX_3_6_3_RELEASE
export REPO='releases/mozilla-1.9.2'
export EMAIL=bhearsum@mozilla.com
export KEYDIR=d:/2009-keys

cd ~/hg-tools
hg pull && hg up -r ${TAG}

mkdir ~/signing-work/${PRODUCT}-${VERSION}
cd ~/signing-work/${PRODUCT}-${VERSION}
cp ~/hg-tools/release/signing/* .

make setup PRODUCT=${PRODUCT} VERSION=${VERSION} BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL} KEYDIR=${KEYDIR} USE_NEW=1
# This step was run a few times, every 10 minutes or so until all builds finished
make download PRODUCT=${PRODUCT} VERSION=${VERSION} BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL} KEYDIR=${KEYDIR} USE_NEW=1
make stubs sign2 stage verify fake-upload PRODUCT=${PRODUCT} VERSION=${VERSION} BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL} KEYDIR=${KEYDIR} USE_NEW=1

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

L10nVerify

The post_signing Scheduler didn't like it was going to fire so I forced a build of this. The Scheduler fired later, and I cancelled that build.
No differences, this is a full PASS.

Generate updates and push betatest snippets

The post_signing Scheduler didn't like it was going to fire so I forced a build of this. The Scheduler fired later, and I cancelled that build.

• Snippet uploads failed because of changes in bug 511967. Need to fix permissions on aus2-staging, or upload with a different user for releases. FIXME file bug to track
• Kicked through manually with:

# cltbld @ moz2-linux-slave43
cd /builds/slave/updates/temp/firefox/3.6.2-3.6.3/
rsync -av -e 'ssh -oIdentityFile=~/.ssh/id_dsa' aus2/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/20100401-Firefox-3.6.3
rsync -av -e 'ssh -oIdentityFile=~/.ssh/id_dsa' aus2.test/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/20100401-Firefox-3.6.3-test
rsync -av -e 'ssh -oIdentityFile=~/.ssh/id_dsa' aus2.beta/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/20100401-Firefox-3.6.3-beta

And then,

# cltbld @ aus2-staging
cd /opt/aus2/snippets/staging
~/bin/backupsnip 20100401-Firefox-3.6.3-test
~/bin/pushsnip 20100401-Firefox-3.6.3-test

Update verify

• Linux: PASS

Update Bouncer

Added with BouncerBuddy.