Releases/Firefox 3.5.17/BuildNotes: Difference between revisions
< Releases | Firefox 3.5.17
Jump to navigation
Jump to search
ChrisCooper (talk | contribs) |
ChrisCooper (talk | contribs) |
||
| Line 128: | Line 128: | ||
* Restarted updates with "Force Build" | * Restarted updates with "Force Build" | ||
** No problems | ** No problems | ||
* the updates builder was triggered a third time, but not sure by what/who. It failed early, and should be harmless. | |||
=== Update Verify === | === Update Verify === | ||
Revision as of 23:14, 24 January 2011
Notes About Releasing
Please update the Release:Primer for future releases (bug fixes, changes to automation) as needed
Build Engineers
bhearsum/coop
bug 624494
Signed-off Revision(s)
Build 1: bc91b067f42f
L10N changesets
Updates l10n-changesets obtained from the l10n shipping dashboard.
Tags
| Build # | Tag | Changeset |
| 1 | FIREFOX_3_5_17_RELEASE FIREFOX_3_5_17_BUILD1 | bc91b067f42f |
Build data
| Build # | Type | Build ID | Build machine | Time to build |
| 1 | Linux | 20110121161846 | linux-ix-slave14 | 29 mins, 15 secs |
| Mac | 20110121150727 | bm-xserve11 | 1 hrs, 41 mins, 34 secs | |
| Windows | 1 hrs, 18 mins, 25 secs | mw32-ix-slave02 | 1 hrs, 18 mins, 25 secs |
Notes
Done on pm01
Build 1
- Set reserved slaves to 4:
# cltbld@pm01 echo 4 > /builds/buildbot/builder_master1/reserved_slaves_pm01
- Clobber won't work for build1 because of bug 626164
- Looked around all of the fast slaves and didn't see anything lying around, so they were clobbered at some point already.
- Landed updated automation config
- Manually tagged buildbot-configs, buildbotcustom, tools with FIREFOX_3_5_17_RELEASE_FIREFOX_3_5_17_BUILD1
- Updated buildbot-configs/buildbotcustom
- Ran release_sanity.py w/ the dry run option:
PYTHONPATH=.:tools/lib/python/ python release_sanity.py -u bhearsum -V 3.5.17 --branch mozilla-1.9.1 --build-number 1 -c release-firefox-mozilla-1.9.1.py --dryrun localhost:9010
- After it passed, ran it without --dry-run to start the release process:
PYTHONPATH=.:tools/lib/python/ python release_sanity.py -u bhearsum -V 3.5.17 --branch mozilla-1.9.1 --build-number 1 -c release-firefox-mozilla-1.9.1.py localhost:9010
Tag
No problems
Source
No problems
Build
- Linux failed to upload symbols
- Clobbered (manually) and re-kicked with "Force Build"
- Linux failed to upload symbols again
- Catlee pointed out that the host key verification was failing
- Logged onto the slave, manually clobbered, fixed the hostkey with:
# cltbld@linux-ix-slave14 ssh -oBatchMode=no dm-symbolpush01.mozilla.org # Typed "yes" when prompted
- Started a new build with "Force Build"
- No problems with Mac or Windows
L10n Repack
- No problems on Mac or Windows
- Had to use "Force Build" with the following properties to start the Linux ones, because of the Linux en-US issues:
release_config: mozilla/release-firefox-mozilla-1.9.1.py script_repo_revision: FIREFOX_3_5_17_RELEASE
XULRunner Source & Build
No problems
Sign
Removed en-US.xpi from candidates directory
Ran the following on the signing machine
PRODUCT=firefox
VERSION=3.5.17
BUILD=1
TAG=FIREFOX_3_5_17_RELEASE
REPO='releases/mozilla-1.9.1'
EMAIL=bhearsum@mozilla.com
KEYDIR=d:/2010-keys
cd ~/hg-tools
hg pull && hg up -r ${TAG}
mkdir -p ~/signing-work/${PRODUCT}-${VERSION}/lib/python
cd ~/signing-work/${PRODUCT}-${VERSION}
cp ~/hg-tools/release/signing/* .
rsync -av ~/hg-tools/lib/python/ ./lib/python/
make autosign PRODUCT=${PRODUCT} VERSION=${VERSION} BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL} KEYDIR=${KEYDIR} USE_NEW=1
And then to upload:
make postsign PRODUCT=${PRODUCT} VERSION=${VERSION} BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL}
Signature verification succeeded.
L10n Verify
- Differences for all locales/platforms because of the shortened build directories.
Updates
- First attempt failed with an ssh key error, on the same slave that had key issues during the Linux build.
- Replaced keys on it with ones from a known good slave:
# cltbld@linux-ix-slave14 su -c 'umount /home/cltbld/.ssh' # multiple times, until fully unmounted rm -rf .ssh scp -r cltbld@mv-moz2-linux-ix-slave08:.ssh .
- Restarted updates with "Force Build"
- No problems
- the updates builder was triggered a third time, but not sure by what/who. It failed early, and should be harmless.
Update Verify
Triggered by hand.
- Linux: No problems
- Mac: No problems
- Win32: No problems
Socorro product data updates
Added '3.5.17' and '3.5.18pre' to crash-stats with this admin page.
Update Bouncer
Added by forcing bouncer_submitter builder
DONE TO HERE
Major Update Generation (-> 3.6.13)
Used 'force build' to start the major_update builder.