Confirmed users
1,351
edits
Release:Release Automation on Mercurial:Starting a Release: Difference between revisions
Release:Release Automation on Mercurial:Starting a Release (view source)
Revision as of 20:42, 25 October 2012
, 25 October 2012TB 10.0.10esr lessons learned
(TB 10.0.10esr lessons learned) |
|||
| Line 70: | Line 70: | ||
= Running release sanity and starting the automation = | = Running release sanity and starting the automation = | ||
On the build scheduler master run release sanity in dry run mode. For example: | On the build scheduler master (see <tt>production-masters.json</tt>, currently bm36) run release sanity in dry run mode. For example (updated for multi-master): | ||
# Combined release | # Combined release | ||
cd /builds/buildbot/ | cd /builds/buildbot/build_scheduler/master | ||
source ../bin/activate | source ../bin/activate | ||
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum \ | PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum \ | ||
| Line 80: | Line 80: | ||
--dryrun localhost:9301 | --dryrun localhost:9301 | ||
# Firefox-only release | # Firefox-only release | ||
cd /builds/buildbot/ | cd /builds/buildbot/build_scheduler/master | ||
source ../bin/activate | source ../bin/activate | ||
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum \ | PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum \ | ||
| Line 87: | Line 87: | ||
--dryrun localhost:9301 | --dryrun localhost:9301 | ||
# Thunderbird release: | # Thunderbird release: | ||
cd /builds/buildbot/ | cd /builds/buildbot/build_scheduler/master | ||
source ../bin/activate | source ../bin/activate | ||
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u hwine \ | PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u hwine \ | ||
| Line 94: | Line 94: | ||
--dryrun localhost:9301 | --dryrun localhost:9301 | ||
After that succeeds (or you account for any failures you receive), run the command again without --dryrun to start the release. | After that succeeds (or you account for any failures you receive), run the command again without --dryrun to start the release. Some standard discrepancies: | ||
* for chemspills: to bypass l10n checks if not changing, add option "<tt>-l</tt>" | |||
* for Thunderbird: to bypass (broken) mozconfig checks, add option "<tt>--bypass-mozconfig-check</tt>" | |||
If you're working in staging you must make sure to pass in the correct staging release config (staging_release-firefox-<branch name>.py) | If you're working in staging you must make sure to pass in the correct staging release config (staging_release-firefox-<branch name>.py) | ||