Releases/Firefox 3.0.4:BuildNotes
< Releases
Jump to navigation
Jump to search
Build Engineers
joduinn or nthomas
Tracking release bug
Bonsai queries
Updated CVS Tags devmo page.
Tags
Build 1:
| Module | Branch | Tag | Pull date |
| cvsroot/mozilla | HEAD | FIREFOX_3_0_4_BUILD1 | 2008-10-28 22:06 PDT |
| l10n/l10n | HEAD | FIREFOX_3_0_4_BUILD1 | 2008-10-28 22:06 PDT |
Build data
| Type | Build ID | SHA1 | Push date | Build machine |
| [Windows installer/zip] | fx-win32-1.9-slave2 | |||
| [Mac compressed] | fx-mac-1.9-slave2 | |||
| [Linux compressed] | fx-linux-1.9-slave2 |
Notes
Build 1
Bootstrap Tag: RELEASE_AUTOMATION_M11
Setup before starting:
- Updated master.cfg, bootstrap.cfg. Retagged bootstrap.cfg.
- On all the slaves:
- ran 'DISPLAY=:0 xhost +' to make sure linux AliveTest works.
- remove /builds/verify/firefox-3.0.2, /builds/verify/firefox-3.0.3
- verified we're using same version of tinderbox as before (RELEASE_AUTOMATION_M11), so nothing to do.
- On the linux slave, removed:
- /builds/updates/firefox-3.0.3
- /builds/source/firefox-3.0.3
- /data/cltbld/firefox-3.0.3
- On the mac slave, removed nothing, as there was loads of space.
- Space on slaves before starting:
- fx-linux-1.9-slave2: 27G on /builds
- fx-mac-1.9-slave2: 22G on /
- fx-win32-1.9-slave2: 16.5G on d:, 2.5G on e: (disk heavy work is done on d, eg update_verify. build/repack is done on e, but mostly just overwrites existing data)
- Gulped, and kicked off automation:
#login to production-1.9-master as buildbot # buildbot sendchange --username=joduinn --master=localhost:9989 -m"Firefox 3.0.4build1 release" go
Tag
- No problems
Source
- No problems
Build & Repack
- linux, mac: No problems
- win32: slave ran out of space during repack:push.
- Even though I'd verified that we had enough free space beforehand - and had more free space then we had when starting FF303. Still dont understand why.
- restarted at just repack:execute, ran to completion just fine.
Sign
- Signing doc
- no problems.
- tweaked master.cfg, and did new sendchange to resume automation from this point.
$ buildbot sendchange --username=joduinn --master=localhost:9989 -m"Firefox 3.0.4build1 release after signing" go
L10nVerify
- Automated - no problems.
Generate Updates
- Automated - no problems.
Publish Updates to Test Channels (betatest & releasetest)
- Automated - no problems.