Releases/Firefox 3.0.14/BuildNotes
Build Engineer(s)
lsblakk
Bonsai queries
Tags
Build 1:
Module | Branch | Tag | Pull date |
cvsroot/mozilla | HEAD | GECKO190_20090824_RELBRANCH FIREFOX_3_0_14_BUILD1 FIREFOX_3_0_14_RELEASE | |
l10n/l10n | HEAD | GECKO190_20090824_RELBRANCH FIREFOX_3_0_14_BUILD1 FIREFOX_3_0_14_RELEASE |
Build 2:
Module | Branch | Tag | Pull date |
cvsroot/mozilla | HEAD | GECKO190_20090824_RELBRANCH FIREFOX_3_0_14_BUILD2 FIREFOX_3_0_14_RELEASE | |
l10n/l10n | HEAD | GECKO190_20090824_RELBRANCH FIREFOX_3_0_14_BUILD2 FIREFOX_3_0_14_RELEASE |
Notes
Build 1
- On fx-win32-1.9-slave2:
- Deleted /e/xr19rel/WINNT_5.2_Depend
- Deleted /e/fx19l10nrel/WINNT_5.2_Depend
- Deleted /e/fx19rel/WINNT_5.2_Depend
- On fx-linux-1.9-slave2:
- Deleted /builds/verify/firefox-3.0.13
- Deleted /builds/verify/firefox-3012-351-major
- Deleted /builds/updates/firefox-3.0.13
- Deleted /builds/source/firefox-3.0.13
- Deleted /builds/tags/FIREFOX_3_0_9_BUILD*
- Deleted /builds/data/cltbld/firefox-3.0.13
- On fx-mac-1.9-slave2:
- Deleted /builds/verify/irefox-20020-3010-major
- Deleted builds/verify/firefox-3012-351-major/
- Space free on slaves:
- fx-mac-1.9-slave2: 21G free on /
- fx-win32-1.9-slave2: 16.4G free on D, 14.1G free on E
- fx-linux-1.9-slave2: 20G free on /builds
- Kicked off automation:
buildbot sendchange --username=lsblakk --master=localhost:9989 -m"Firefox 3.0.14build1 release" go
Tag
No problems
Source
No problems
Build & Repack
- Linux - no problems
- Mac - no problems
- Win32 - no problems
Sign
- Signing doc
- no problems
L10nVerify
- no problems - no l10n changes
Generate Updates
We ran into a problem on the very first Mac update creation - make_incremental_updates.py didn't have file paths in quotations for the mbsdiff call and so because there was a change to Contents/MacOS/plugins/Default Plugin the attempt to do a patch failed due to spaces in the shell command call.
Filed bug 512477 to fix this issue, clobbered builds/updates/firefox-3.0.14 on fx-linux-1.9-slave2, commented out the PatcherConfig step in production-1.9-master's master.cfg, reconfig'd and forced build on update again.
Publish Updates to Test Channels (betatest & releasetest)
- This is now automated in the Update step (see logs for push)
Update Verify
- linux - full PASS
- win32 - .chk files differ, as always, otherwise find.
- mac - full PASS
Stage
No problems
XULRunner
No problems
At this point the release process was interrupted by bug 510583
Build 2
- On fx-win32-1.9-slave2:
- Deleted /e/xr19rel/WINNT_5.2_Depend
- Deleted /e/fx19l10nrel/WINNT_5.2_Depend
- Deleted /e/fx19rel/WINNT_5.2_Depend
- On fx-linux-1.9-slave2:
- Deleted /builds/verify/firefox-3013-352-major
- Deleted /builds/verify/firefox-3.0.13
- Deleted /builds/verify/firefox-3012-351-major
- Deleted /builds/verify/firefox-3.0.14
- Deleted /builds/updates/firefox-3.0.14
- Deleted /builds/source/firefox-3.0.14
- Deleted /builds/tags/FIREFOX_3_0_10 & FIREFOX_3_0_11*
- Deleted /builds/data/cltbld/firefox-3.0.14
- Deleted /builds/tinderbox/Xr-Mozilla
- On fx-mac-1.9-slave2:
- Deleted /builds/verify/*
- Space free on slaves:
- fx-mac-1.9-slave2: 20G free on /
- fx-win32-1.9-slave2: 16.4G free on D, 14.1G free on E
- fx-linux-1.9-slave2: 25G free on /builds
- Kicked off automation
buildbot sendchange --username=lsblakk --master=localhost:9989 -m"Firefox 3.0.14build2 release" go
Tag
No problems
Source
No problems
Build & Repack
- Linux - had to do a couple of force builds because on the first run through my attempt to recreate the tinderbox dir in fx-linux-1.9-slave2 (after accidentally wiping it for Fx-Mozilla1.9-Release) had bad symlinks, then a second force because of having to comment out the TinderConfig step
- No problems on Win32 or Mac
Sign
- Signing doc
- NB: Doc change - Made the old signing steps more obvious so as to avoid trying to do them.
- no problems
L10nVerify
No l10n changes at all
Generate Updates
No problems with update generation
Publish Updates to Test Channels (betatest & releasetest)
No problems
Update Verify
- linux - full PASS
- win32 - .chk files differ, as always, otherwise fine.
- mac - full PASS
Stage
No problems
XULRunner
No problems
3.0.14 -> 3.5.x Major Update Refresh
version bumps for patcher config and release/update
Snippet Generation
mkdir -p /builds/3.0.14-3.5.3-major-update/snippets cd /builds/3.0.14-3.5.3-major-update/snippets
cvs -d:ext:ffxbld@cvs.mozilla.org:/cvsroot co -d patcher-configs mozilla/tools/patcher-configs cvs -d:ext:ffxbld@cvs.mozilla.org:/cvsroot co -r UPDATE_PACKAGING_R9 -d patcher mozilla/tools/patcher cd patcher cvs -d:ext:ffxbld@cvs.mozilla.org:/cvsroot co -r UPDATE_PACKAGING_R9 -d MozBuild mozilla/tools/release/MozBuild
export CVSROOT=:ext:ffxbld@cvs.mozilla.org:/cvsroot
- build tools
./patcher2.pl --build-tools --app=firefox --tools-rev=UPDATE_PACKAGING_R9 --config=../patcher-configs/moz19-branch-major-update-patcher2.cfg 2>&1 | tee ../firefox_build-tools.log
- download mars
./patcher2.pl --download --app=firefox --config=../patcher-configs/moz19-branch-major-update-patcher2.cfg 2>&1 | tee ../firefox_download.log
- FIXME - patcher needs to see that the MARs that it thinks are partials
- are there or else it will not attempt to generate patchinfo
cd temp/firefox ln -s 3.5.3 3.0.14-3.5.3 cd ../..
- Create partial patches and snippets
./patcher2.pl --create-patches --app=firefox --config=../patcher-configs/moz19-branch-major-update-patcher2.cfg 2>&1 | tee ../firefox-create-patches.log