Firefox 3.0b5:BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 69: Line 69:
==RC1==
==RC1==


Bootstrap tag: RELEASE_AUTOMATION_M7_2
Bootstrap tag: RELEASE_AUTOMATION_M8


Setup before starting:
Setup before starting:

Revision as of 09:20, 26 March 2008

Build Engineers

Bonsai queries

Bugs

Tracking bug for Firefox 3.0beta5 bug 424242

(yes, yes, the answer to the ultimate question!)

Tags

Module Tag Pull date
cvsroot/mozilla
l10n/l10n

Build data

Type Build ID SHA1 Push date Build machine
[Windows installer]
[Mac compressed]
[Linux compressed]

Notes

RC1

Bootstrap tag: RELEASE_AUTOMATION_M8

Setup before starting:

  • Profile Guided Optimisation
    • need at least rev1.383 of tinderbox/build-seamonkey-util.pm when tagging tinderbox
    • for the Windows slave
      • bring over the mk_add_options PROFILE_GEN_SCRIPT... line from the nightly mozconfig to the release one, and the tweaks to CFLAGS & CXXFLAGS
      • Also pick up the new jemalloc line and removal of WIN32_REDIST_DIR
      • bring over $ProfiledBuild = 1; from nightly tinder-config.pl to release one
      • Bump fx-win32-1.9-slave2 up to 2GB of RAM, to match nightly VM
  • used existing version bump bug to attached diff for bootstrap.cfg and master.cfg
    • make sure /builds/buildbot/trunk-automation-master/bootstrap.cfg is updated
    • restarted master
  • compare nightly and release mozconfig/tinder-config.pl files, merge any desired changes
  • On fx-mac-1.9-slave2, fx-win32-1.9-slave2, fx-linux-1.9-slave2
    • REMEMBER to use VNC when restarting mac slave
    • verify that both mac and linux have "xhost +" since last reboot
    • update tinderbox to RELEASE_AUTOMATION_M7_2
      • FIXME update should be automatic - bug 397554
      • cd /builds/tinderbox/mozilla/tools/tinderbox
      • cvs up -r RELEASE_AUTOMATION_M7_2
    • remove the contents of /builds/verify/*
      • FIXME should be automatically backed up or removed - bug 413178
    • restart buildbot
  • On production-1.9-master
    • remove the contents of /builds/updates/
    • remove private and public areas
      • rm -rf /data/cltbld/firefox-*
      • rm -rf /builds/tags/* - did not do this, plenty of space
      • in /home/ftp/pub/firefox/nightly/, remove all except the 3.x-candidates directory for the previous release
        • rm -rf /home/ftp/pub/firefox/nightly/2007*
        • FIXME should not be needed - bug 415970
  • af was not tagged, so had to checkout a tagged locale so CVS would cache it
    • cvs co -r FIREFOX_3_0b4_RELEASE l10n/de
  • kick off buildbot (run as cltbld):
buildbot sendchange --username=joduinn --master=localhost:9989 -m "Firefox 3.0 Beta 4 RC1" release

Prestage

Tag

Source

Build

Sign

L10nVerify

Updates to Test Channel

  • Make sure the new patcher config changes are used. patcherToolsRev should be UPDATE_PACKAGING_R2. snippets should have prettyVersion (3 Beta 5) as their appv. Patcher-created directory structure should use unpretty version (3.0b5).

update Verify

Stage

Sign Installers

Update Bouncer

Final Verification

Push to mirrors

Updates to Beta Channel

In case you need to cancel/abort updates, the quickest way to do this is [1]

  • While waiting for formal "go", backup existing beta channel
 # login to aus2-staging
 $ sudo su - cltbld
 # make sure using latest version of scripts
 $ cvs get -d bin mozilla/tools/release/bin/ 
   cvs checkout: Updating bin
 $ cd /opt/aus2/snippets/staging
 # note the required parameter must match what will be used with pushsnip below. 
 $ ~/bin/backupsnip 20080308-Firefox-3.0b4
  • Once QA and Website gives formal "go" to put updates on beta channel
 # login to aus2-staging
 $ sudo su - cltbld
 # make sure using latest version of scripts
 $ cvs get -d bin mozilla/tools/release/bin/ 
   cvs checkout: Updating bin
 $ cd /opt/aus2/snippets/staging
 $ ~/bin/pushsnip 20080308-Firefox-3.0b4

Wall clock timings