Releases/Firefox 3.0.1:BuildNotes

Build Engineers

bhearsum
Version/config bump bug

Tags

Build 1:

Module	Branch	Tag	Pull date
cvsroot/mozilla
l10n/l10n

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_M10

Setup before starting:

• Updated master.cfg, bootstrap.cfg. Retagged bootstrap.cfg.
• On the slaves:
• verify that linux has 'DISPLAY=:0 xhost +' set
• remove /builds/verify/firefox-3.0rc3 and firefox-3.0rc2
• update tinderbox to RELEASE_AUTOMATION_M10
  • For win32:

cd /e/builds/tinderbox/mozilla/tools/tinderbox
cvs up -r RELEASE_AUTOMATION_M9_1
for dir in fx19rel fx19l10nrel xr19rel; do 
  cd /e/$dir; 
  for f in `ls *.pl *.html INSTALL README | grep -v tinder-config.pl`; do 
    cp -pv /e/builds/tinderbox/mozilla/tools/tinderbox/$f .;
  done
  cp -pv post-mozilla-rel.pl post-mozilla.pl
done

• On the linux slave, removed:
  • /builds/updates/firefox-3.0rc3
  • /builds/source/*
  • /data/cltbld/firefox-3.0rc3
• For some reason bm-xserve11 was attached to the buildbot master.
  • Disconnected it, and reconnected the proper slave (bm-xserve10/fx-mac-1.9-slave2
• Space on slaves before starting:
  • fx-linux-1.9-slave2: 29G on /builds
  • fx-mac-1.9-slave2: 24G on /
  • fx-win32-1.9-slave2: 17G on d:, 2G on e: (disk heavy work is done on d, eg update_verify. build/repack is done on e, but mostly just overwrites existing data)

• Disabled everything after Updates::Push in master.cfg (local modification) because additional patcherconfig/update work needs to be done after Updates::execute but

before updates::push.

• Gulped, and kicked off automation:

buildbot sendchange --username=bhearsum --master=localhost:9989 -m"Firefox 3.0.1build1 release" gogogo