Releases/Firefox 3.5rc2/BuildNotes
Contents
Build Engineers
nthomas/bhearsum
release tracking bug
Signed-off Revision(s)
Build1: cba3751c7311
Build2: dbb1982adfab
Tags
On releases/mozilla-1.9.1:
| Build # | Tag | Changeset |
| 1 | GECKO191_20090616_RELBRANCH | cba3751c7311 |
| FIREFOX_3_5rc2_BUILD1 | f9c0198d335b | |
| 2 | FIREFOX_3_5rc2_BUILD2 FIREFOX_3_5rc2_RELEASE | dbb1982adfab |
Build data
| Type | Build ID | Build machine |
| [Windows installer/zip] | 20090616224221 | |
| [Mac compressed] | 20090616212246 | |
| [Linux compressed] | 20090616212416 |
Notes
Build 1
- clean up directories on slaves from 3.5rc1 build2 (everything but in particular the repack dirs)
- patch buildbot-configs/mozilla2/release_config.py, and get review. Add the driver specified changeset and land the change
- land l10n-changesets bump from bug 498757
- reconfig production-master
- do sendchange
buildbot sendchange --username=nthomas --master=localhost:9010 --branch=releases/mozilla-1.9.1 -m "Firefox 3.5rc2 build1" goforit
Tag
No problems.
Source
No problems.
Build/Repack
No problems with Linux, then drivers asked to take another two changes. Aborted Mac and Windows en-US builds. RESPIN DECLARED
Build 2
- clean up directories on slaves from 3.5rc2 build1 (everything but in particular the repack dirs)
- IT had one half of hg.m.o down for maintenance and didn't reconfigure DNS ahead of time. Did lookupd -flushcache on the mac machines as I'd had trouble using it, linux seems to be fine, and we're beyond the 1 hour that Windows caches for.
- patch buildbot-configs/mozilla2/release_config.py, and get review; land.
- reconfig production-master
- do sendchange
buildbot sendchange --username=nthomas --master=localhost:9010 --branch=releases/mozilla-1.9.1 -m "Firefox 3.5rc2 build2" goforit
Tag
No problems.
Source
No problems.
Build/Repack
No problems. Removed stage:.../3.5rc2-candidates/build2/en-US.xpi.
Sign
instructions No problems
L10nVerify
Absolutely nothing in here except for lines with differences in the absolute slave path (/builds/moz2_slave vs. /builds/slave).
Generate updates and push betatest snippets
Need to do this trick again between the config bump and building update. Forgot to update the patcher-configs checkout on the slave, had to kill the builder and restart from the --create-patches step. After that, realized we couldn't guarantee it would run on the same slave, so commented out only the patcher and update verify bumping steps, and started again. Worked fine after doing this, backed out the patch.
NB: beta and release snippets got put into the same directory. This is OK since we want to update rc1 -> rc2 at the same time as going to beta. we need to flip useBetaChannel when we do our first point release, though.
bug 498990 QA reported a problem with 3.5rc1build2 not updating correctly. Pinged Mossop and he told me that 3.5rc1 requires snippets that have 'extv=3.5'. 3.5b2 -> 3.5b99 won't work with that, so we must modify *only* the 3.5rc1 snippets. (This is the only the case for the RCs, everything works again once we hit 3.5.1). Here's how I fixed the snippets:
# cltbld@aus2-staging
cd ~/
rsync -av /opt/aus2/snippets/staging/20090617-Firefox-3.5rc2-test/ 20090617-Firefox-3.5rc2-test-3.5rc1-fix/
cd 20090617-Firefox-3.5rc2-test-3.5rc1-fix/Firefox
rm -rf 3.1a1 3.1a2 3.1b1 3.1b2 3.1b3 3.5b4 3.5b99
find . -type f -exec sed -i -e 's/extv=3.5rc2/extv=3.5/' {} \;
# this next command should print out a bunch of 'extv=3.5' lines
find . -type f -exec grep extv {} \;
cd ../../
# now the test channel
cd ~/
rsync -av /opt/aus2/snippets/staging/20090617-Firefox-3.5rc2/ 20090617-Firefox-3.5rc2-3.5rc1-fix/
cd 20090617-Firefox-3.5rc2-3.5rc1-fix/Firefox
rm -rf 3.1a1 3.1a2 3.1b1 3.1b2 3.1b3 3.5b4 3.5b99
find . -type f -exec sed -i -e 's/extv=3.5rc2/extv=3.5/' {} \;
# this next command should print out a bunch of 'extv=3.5' lines
find . -type f -exec grep extv {} \;
# now rsync these snippets over to the staging area rsync -av 20090617-Firefox-3.5rc2-test-3.5rc1-fix /opt/aus2/snippets/staging/ rsync -av 20090617-Firefox-3.5rc2-3.5rc1-fix /opt/aus2/snippets/staging/
# backupsnip before repushing the test snippets ~/bin/backupsnip 20090617-Firefox-3.5rc2-test-3.5rc1-fix ~/bin/pushsnip 20090617-Firefox-3.5rc2-test-3.5rc1-fix
Update verify
- In the first half of the logs for each platform we had differences channel-prefs.js. This is expected because this is the first release we've shipped on the 'release' channel.
- All platforms threw 'download_mars' errors on 3.5b4 mn, tr because they were shipped in 3.5b4 but not in 3.5rc1. These lines are ignorable.
- Win32 threw the usual messages about .chk files.
- No real problems here.
Update Bouncer
Done
Final checks before push
Each of the find calls should return no output.
cd /pub/mozilla.org/firefox/nightly/3.5rc2-candidates/build2/ find . ! -user ffxbld find . ! -group firefox find . -type f ! -perm 644 find . -type d -mindepth 1 ! -perm 755 ! -name 'contrib*' find . -type d -maxdepth 1 ! -perm 2775 -name 'contrib*'
The first find produced some solaris builds in contrib, this is OK.
Push to mirrors
# root@stage (done by dmoore) mkdir /home/ftp/pub/firefox/releases/3.5rc2/ chown ffxbld /home/ftp/pub/firefox/releases/3.5rc2/
FIXME: need to figure out a better solution than this directory creation.
# ffxbld@stage rsync -av --exclude=*.log --exclude=*.txt --exclude=*unsigned* \ /pub/mozilla.org/firefox/nightly/3.5rc2-candidates/build2/ \ /pub/mozilla.org/firefox/releases/3.5rc2/
# cltbld@stage vim /pub/mozilla.org/zz/rsyncd-mozilla-current.exclude # replace 3.5rc1 with 3.5rc2.
cd /pub/mozilla.org/firefox/releases/ rm latest-3.5 && ln -s 3.5rc2 latest-3.5
Final Verification
Use 'Force Build to start the final_verification builder, no errors other than the same warnings as update verify (mn & tr were dropped in rc1)
Publish updates to beta channel
~/bin/backupsnip 20090617-Firefox-3.5rc2 ~/bin/pushsnip 20090617-Firefox-3.5rc2 ~/bin/pushsnip 20090617-Firefox-3.5rc2-3.5rc1-fix
