Releases/Firefox 3.5b4/BuildNotes

From MozillaWiki
Jump to navigation Jump to search

Build Engineers

nthomas/bhearsum
release tracking bug

Signed-off Revision(s)

Build1: rev 5b61f163f2fd

Tags

On release/mozilla-1.9.1:

Build # Tag Changeset
1 GECKO191b4_20090423_RELBRANCH 5b61f163f2fd
FIREFOX_3_5b4_RELEASE FIREFOX_3_5b4_BUILD1 afac8b5958bc

All l10n repositories listed in l10n-changesets were also relbranch'd to GECKO191b4_20090423_RELBRANCH, and tagged with FIREFOX_3_5b4_RELEASE and FIREFOX_3_5b4_BUILD1 for build1.

Build data

Type Build ID Build machine
[Windows installer/zip] 20090423204732
[Mac compressed] 20090423191946
[Linux compressed] 20090423192432

Notes

  • moved UPDATE_PACKAGING_R7 to 0f80ac6c75d8 (tip at the time) in build/tools repo to pick up bug 487677

Build 1

  • patch buildbot-configs/mozilla2/release_config.py, get review, land
  • checkin latest copy of l10n-changesets from tracking bug
  • reconfig production-master
  • do sendchange
buildbot sendchange --username=nthomas --master=localhost:9010 --branch=releases/mozilla-1.9.1 -m "Firefox 3.5b4 build1" goforit

Tag

No problems. Landed the version bump to 3.5b5pre, need push -f to create a new head (make sure you are on the default branch!).

Source

No problems.

Build/Repack

Slave for Windows build was interrupted by mistake, stopped linux & mac en-US builds and cleaned up all three slaves. Added a dummy_factory and used it for tag and source steps, reconfig'd master and did sendchange. No problems with mac or linux. Windows running.

Discovered localised complete mars missing, filed bug 489954 and put in a temporary fix.

Assorted more sendchanges to deal with

  • moz2-win32-slave22 still having a 3.1b3 checkout and getting stuck on the relbranch for that (need newer hg or more careful cleanup or better source pull logic)
  • moz2-win32-slave05 getting a busted mozilla-1.9.1 repo
  • getting some connection resets on upload to stage
  • not thinking as clearly as is useful

We have 70 complete mars for each platform now. It would be _really_ great if we had a way to trigger only some locale & platform combinations.

Sign

instructions

  • Failed out when stub files couldn't be checked out.
    • Had to re-install the Equifax root certificate (because of the recent cygwin update):
cp equifax.pem /usr/ssl/certs
echo "ca_certificate = /usr/ssl/certs/equifax.pem" >> /etc/wgetrc
  • Restarted with:
make sign PRODUCT=$PRODUCT VERSION=$VERSION BUILD=$BUILD TAG=$TAG REPO=$REPO EMAIL=bhearsum@mozilla.com

STILL TO DO: 

make stage verify fake-upload PRODUCT=$PRODUCT VERSION=$VERSION BUILD=$BUILD TAG=$TAG REPO=$REPO EMAIL=bhearsum@mozilla.com

Plus the rest real upload of the builds and the logfile, as documented on the signing instructions page.

L10nVerify

Generate updates and push betatest snippets

NOT DONE YET

  • Updates builder should kick off automatically shortly after the win32 signing log has been uploaded to the candidates directory
  • If all goes well, updates will be pushed out to their proper location in the candidates dir and the update_verify builders will be kicked off

Update verify

NOT DONE YET

  • Look for failures in the update verify logs, figure out if they legitimate or not


Update Bouncer

  • Done.

Final checks before push

NOT DONE YET 

cd /home/ftp/pub/firefox/nightly/3.5b4-candidates/build1/
find . ! -user ffxbld
find . ! -group firefox
find contrib contrib-localized ! -perm 2775

Push to mirrors

NOT DONE YET 

# ffxbld@stage
rsync -av --exclude=*.log --exclude=*.txt --exclude=*unsigned* \
 /home/ftp/pub/firefox/nightly/3.5b4-candidates/build1/ \
 /home/ftp/pub/firefox/releases/3.5b4/

Final verification

NOT DONE YET

  • Use 'Force Build to start the final_verification builder, chase down any 503 or 404 errors to find bad mirrors

Publish updates to beta channel

NOT DONE YET 

time ~/bin/backupsnip 20090424-Firefox-3.5b4
time ~/bin/pushsnip 20090424-Firefox-3.5b4
Retrieved from "https://wiki.mozilla.org/index.php?title=Releases/Firefox_3.5b4/BuildNotes&oldid=141563"