Releases/Firefox 3.5rc1/BuildNotes
Build Engineers
nthomas/bhearsum
release tracking bug
Signed-off Revision(s)
Build1:
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
- clean up directories on slaves from 3.5b99 (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
- checkin latest copy of l10n-changesets from the l10n tracking bug
- reconfig production-master
- do sendchange
buildbot sendchange --username=bhearsum --master=localhost:9010 --branch=releases/mozilla-1.9.1 -m "Firefox 3.5rc1 build1" goforit
Build 1
Tag
Hung on the first 'hg out' because the slave it was running on didn't have the host key for hg.mozilla.org accepted. Went around and accepted the host key on all slaves (not just Linux), cleaned out the tag directory on moz2-linux-slave19, and restarted. Tagging worked fine afterwards.
Source
No problems
Build/Repack
No problems with Linux build or l10n. No problems with Mac build or l10n. No problems with Win32 build or l10n.
TODO prioritize release builders above others or use different slave set for l10n. mac l10n took awhile to start because the nightly builds got triggered first.
Removed .../build1/en-US.xpi, which is not handled properly until bug 485860 is fixed.'
Sign
- Failed out first time due to disk space. Cleared some space and restarted it
- No problems on second run
- Everything after this manually triggered because of bug 479041
L10nVerify
No problems. Lots of path differences in comments in firefox-l10n.js on linux and mac, and gl updating some bookmarks strings.
Generate updates and push betatest snippets
moz2-linux-slave19 hadn't had stage-old.m.o's signature accepted, so partial uploads could not be uploaded. Fixed there and on slave18 to make whole pool OK, fixed linux refplatform doc.
The failure is actualy helpful, as we need to deal with the same issue as bug 496917 - that we can't use appv=3.5 RC 1, and in fact have to use just appv=3.5 in order for bug 313057 to work as planned.