Firefox 2.0.0.12:BuildNotes: Difference between revisions

(separate backup from deploy)
 
(5 intermediate revisions by the same user not shown)
Line 295: Line 295:


====Sign Installers====
====Sign Installers====
* ''NOTE'' - build-console is no longer used from here on
* pull stage:/data/cltbld/firefox-2.0.0.12/batch1/stage-signed/ to signing machine
* follow installer-signing-instructions [https://intranet.mozilla.org/Build:Unified_Release_Process#Sign_builds here]
* push signed bits back to same location on stage
* complete stage-merged:
# on stage
cd /data/cltbld/firefox-2.0.0.12/
rsync -av batch1/mar/ stage-merged/
rsync -av batch1/stage-signed/ stage-merged/
* Create MD5 and SHA1 checksum files
# on stage
cd /data/cltbld/firefox-2.0.0.12/stage-merged/
~/bin/checksum-files .
* Fix permissions & ownership (on the two SUM files, and the detached sigs)
chown -R cltbld:firefox .
chmod 644 *SUMS
====Release====
====Release====
* get the last formal "go" from QA/Dev/website/IT/release-drivers
* push the stage-merged directory to the releases area:
# on stage
rsync -av /data/cltbld/firefox-2.0.0.12/stage-merged/ /home/ftp/pub/firefox/releases/2.0.0.12/
* After pushing live, move forward the "latest" and "latest-2.0" symlinks:
  cd /home/ftp/pub/firefox/releases/
  rm latest
  ln -s 2.0.0.12 latest
  rm latest-2.0
  ln -s 2.0.0.12 latest-2.0
* Update stage:/etc/rsyncd-mozilla-current.exclude
====Update Bouncer====
====Update Bouncer====
* Add entries to download.mozilla.org
====Final Verification====
====Final Verification====
Verify that releasetest points to valid bouncer links:
# this can be run from anywhere
cvs co mozilla/testing/release
cd mozilla/testing/release/updates
cat moz18-firefox-*.cfg | sed 's/betatest/releasetest/' | grep -v 2.0a | grep -v 2.0b > update.cfg
./verify.sh -t update.cfg 2>&1 | tee quickVerify.log
Look for any HTTP error codes besides 200 ("OK") and 302 ("Found"):
grep HTTP quickVerify.log | grep -v 200 | grep -v 302
Before pushing final updates,verify that "release" and "releasetest" channel match:
# on aus2-staging
cd /opt/aus2/snippets/staging/20080203-Firefox-2.0.0.12
find -type d -iregex '.*release.*' | perl -nle '$a = $_; $a =~ s/release/releasetest/; system("diff -r -u $_ ../20080203-Firefox-2.0.0.12-test/$a");'
====Enable update channel====
====Enable update channel====
* Wait for QA to finish testing update snippets on releasetest channel, then enable update snippets on release channel
  # on aus2-staging
  # put snippets on release/live channel
  $ cd /opt/aus2/snippets/staging
  $ sudo su - cltbld
  $ ~/bin/pushsnip 20080203-Firefox-2.0.0.12
====Free Software builds====
====Free Software builds====
* Bump the BuildTag definition in the three tinder-config.pl, [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=MOZILLA_1_8_BRANCH_release_free_software&branchtype=regexp&dir=mozilla%2Ftools%2Ftinderbox-configs%2F&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=day&mindate=2008-02-07+08%3A00&maxdate=2008-02-07+08%3A45&cvsroot=%2Fcvsroot like this]
* Done on production machines:
** production-pacifica-vm (win32)
** bm-xserve05 (macosx)
** production-prometheus-vm (linux)
* Start builds:
cd /builds/tinderbox/Fx-Mozilla1.8-FS
./build-seamonkey.pl --once --depend --config-cvsup-dir `pwd`/tinderbox-configs/ 2>&1 | tee FIREFOX_2_0_0_12_FS.log
* Stage
# as cltbld@stage
mkdir -p ~/firefox-2.0.0.12-fs/batch1/prestage
cd ~/firefox-2.0.0.12-fs/batch1
# rsync from push dirs
rsync -av /home/ftp/pub/firefox/nightly/2008-02-07-09-mozilla1.8-fs/ ./prestage/
rsync -av prestage/ prestage-trimmed/
rm -v prestage-trimmed/*.zip
rsync -av prestage-trimmed/ stage/
cd stage
~/bin/groom-files --long="2.0.0.12.fs" .
chown -R cltbld:firefox * .
find . -type f -exec chmod -v 644 {} \;
find . -type d -exec chmod -v 755 {} \;
cd ../
rsync -av stage/ /home/ftp/pub/firefox/releases/2.0.0.12/contrib/free-software/


=== Wall clock timings ===
=== Wall clock timings ===
Confirmed users
4,293

edits