Releases/Firefox 3.5.1/BuildNotes

Build Engineers

nthomas/bhearsum
release tracking bug

Tags

On releases/mozilla-1.9.1:

Build #	Tag	Changeset
1

Build data

Type	Build ID	Build machine
[Windows installer/zip]
[Mac compressed]
[Linux compressed]

Notes

Build 1

• Cleaned up previous release's build dirs
• l10n-changesets updated in bug 502627
• Land version bump, reconfig production-master
• Kick-off automation:

buildbot sendchange --username=bhearsum --master=localhost:9010 --branch=releases/mozilla-1.9.1 -m "Firefox 3.5.1 build1" goforit

Tag

Tag blew up on pt-BR. Pike fixed it and it was pushed manually from moz2-linux-slave10 like so:

hg push -e 'ssh -l ffxbld -i ~cltbld/.ssh/ffxbld_dsa' -f ssh://hg.mozilla.org/releases/l10n-mozilla-1.9.1/pt-BR

To finish off the tagging, had to land patch, reconfig buildbot, and do the sendchange again. The patch was left in until repacks started because a reconfig would prevent Dependent schedulers from firing. No problems after that

Source

No problems

Build/Repack

• Linux
  • No build problems
  • A bunch of repacks blew up because some slaves weren't cleaned up properly.
  • To fix, landed and reconfig for patch and re-kicked automation:

buildbot sendchange --username=bhearsum --master=localhost:9010 --branch=releases/mozilla-1.9.1 -m "Firefox 3.5.1 build1" goforit

• Mac
  • Repack needs to be kicked in the same way as Linux with | this patch and then:

buildbot sendchange --username=bhearsum --master=localhost:9010 --branch=releases/mozilla-1.9.1 -m "Firefox 3.5.1 build1" goforit

• Win32
  • Repack needs to be kicked in the same way as Linux with | this patch and then:

buildbot sendchange --username=bhearsum --master=localhost:9010 --branch=releases/mozilla-1.9.1 -m "Firefox 3.5.1 build1" goforit

• Had to delete en-US.xpi from stage

Sign

instructions No problems

L10nVerify

• Nothing of note

Generate updates and push betatest snippets

• Failed out because UPDATE_PACKAGING_R9 tag wasn't created in mozilla-1.9.1.
  • Tagged the UPDATE_PACKAGING_R8 revision with UPDATE_PACKAGING_R9 and started from scratch.
• While backupsnip was running I noticed that beta snippets were pointing to bouncer, and not in their own directory. This patch plus the following commands run on moz2-linux-slave22 fixed us up:

cd /builds/slave/updates/build/temp/firefox/3.5rc3-3.5.1
mv aus2 aus2.BAD
mv aus2.test aus2.BAD
cd /builds/slave/updates/build/patcher-configs
cvs up
cd /builds/slave/updates/build
perl patcher2.pl --create-patchinfo --partial-patchlist-file=patchlist.cfg --app=firefox --brand=Firefox --config=patcher-configs/moz191-branch-patcher2.cfg
cd temp/firefox/3.5rc3-3.5.1
rsync -av aus2/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/20090715-Firefox-3.5.1
rsync -av aus2.beta/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/20090715-Firefox-3.5.1-beta
rsync -av aus2.test/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/20090715-Firefox-3.5.1-test

Then on aus2-staging

# cltbld
cd /opt/aus2/snippets/staging
~/bin/backupsnip 20090715-Firefox-3.5.1-test
~/bin/pushsnip 20090715-Firefox-3.5.1-test

todo We need to flip useBetaChannel for the next release, and maybe do more. I haven't had a chance to test if the patcher config bump script is broken or not.

Update verify

• Linux timed out after a very, very slow download
  • Kicked a second run - turned green, no problems
• Win32 had the normal .chk file errors, otherwise ok
• Mac - turned green, no problems in log

Publish updates to beta channel

NOT DONE YET

# cltbld @ aus2-staging
cd /opt/aus2/snippets/staging
~/bin/backupsnip 20090715-Firefox-3.5.1-beta
~/bin/pushsnip 20090715-Firefox-3.5.1-beta

Update Bouncer

Done