Releases/Thunderbird 14.0b3/BuildNotes: Difference between revisions
< Releases
Jump to navigation
Jump to search
ChrisCooper (talk | contribs) |
|||
| (9 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Thunderbird:BuildNotes]] | [[Category:Thunderbird:BuildNotes]] | ||
= Bugs hit = | = Bugs hit = | ||
* {{bug|757798}} - Enabled hgtool.py for many builders. Turns out that it didn't work with repacks, had to back out that part of the patch. | |||
=Build 1= | =Build 1= | ||
| Line 15: | Line 16: | ||
* Update l10n changesets & hit "ship it" | * Update l10n changesets & hit "ship it" | ||
wget -O mozilla/l10n-changesets_thunderbird-beta https://l10n.mozilla.org/shipping/l10n-changesets?ms=tb14_beta_b3 | wget -O mozilla/l10n-changesets_thunderbird-beta https://l10n.mozilla.org/shipping/l10n-changesets?ms=tb14_beta_b3 | ||
* Land automation configs | * Land automation configs | ||
* Tag buildbot-configs, buildbotcustom, & tools with build & release tags. | * Tag buildbot-configs, buildbotcustom, & tools with build & release tags. | ||
** hg tag THUNDERBIRD_14_0b3_{RELEASE,BUILD1} | ** hg tag THUNDERBIRD_14_0b3_{RELEASE,BUILD1} | ||
* update and reconfigure the master | * update and reconfigure the master | ||
* release sanity dry run | |||
<pre> | <pre> | ||
cd /builds/buildbot/build1/master | cd /builds/buildbot/build1/master | ||
source ../bin/activate | source ../bin/activate | ||
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u coop -V 14.0b3 \ | PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u coop -V 14.0b3 \ | ||
--branch comm-beta --build-number 1 \ | --branch comm-beta --build-number 1 \ | ||
| Line 42: | Line 31: | ||
* start automation | * start automation | ||
<pre> | <pre> | ||
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u coop -V 14.0b3 \ | |||
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u | |||
--branch comm-beta --build-number 1 \ | --branch comm-beta --build-number 1 \ | ||
--release-config release-thunderbird-comm-beta.py --products thunderbird \ | --release-config release-thunderbird-comm-beta.py --products thunderbird \ | ||
-m -l localhost:9001 | -m -l localhost:9001 | ||
</pre> | </pre> | ||
* | * monitor progress on buildbot, i.e. [http://buildbot-master34.srv.releng.scl3.mozilla.com:8001/waterfall?category=release-comm-beta- release-comm-beta] | ||
== Check that the builds are taken after tagging == | == Check that the builds are taken after tagging == | ||
| Line 67: | Line 43: | ||
== Branches glog == | == Branches glog == | ||
* Check that tagging created the branches and document them | * Check that tagging created the branches and document them | ||
http://hg.mozilla.org/releases/mozilla-beta/graph/ | http://hg.mozilla.org/releases/mozilla-beta/graph/96128 | ||
http://hg.mozilla.org/releases/comm-beta/graph/11884 | http://hg.mozilla.org/releases/comm-beta/graph/11884 | ||
| Line 73: | Line 49: | ||
Use the address "metrics-alerts < AT > mozilla < PERIOD > org". <small><em>Note for first-time-releasers: your email will get held for moderator approval - that is expected. If it happens more than once, get help on <tt>#metrics</tt>.</em></small> | Use the address "metrics-alerts < AT > mozilla < PERIOD > org". <small><em>Note for first-time-releasers: your email will get held for moderator approval - that is expected. If it happens more than once, get help on <tt>#metrics</tt>.</em></small> | ||
Thunderbird,thunderbird,thunderbird,14.0b3,14.0 | Thunderbird,thunderbird,thunderbird,14.0b3,14.0 | ||
== l10n repacks == | |||
* all repacks failed | |||
** bhearsum did the following: | |||
*** Repacks failed because {{bug|757798}} added an invalid path to hgtool.py. [https://bugzilla.mozilla.org/attachment.cgi?id=634856&action=edit This patch] was double landed (default + production branch) as a fix, and I moved the THUNDERBIRD_14_0b3_{RELEASE,BUILD1} tags to pick it up. | |||
*** After that, the repacks got further along but kept failing because they were trying to update the mozilla-beta repo to 'releases/comm-beta'. It became apparent at that point that hgtool.py was never known to work with repacks, so I backed it out for l10n with [https://bugzilla.mozilla.org/attachment.cgi?id=634866&action=edit this patch]. | |||
== Reset reserved slaves == | == Reset reserved slaves == | ||
[cltbld@buildbot-master34 master]$ echo "0" > /builds/buildbot/build1/master/reserved_slaves | |||
== Going to Beta == | == Going to Beta == | ||
Latest revision as of 14:08, 10 August 2012
Bugs hit
- bug 757798 - Enabled hgtool.py for many builders. Turns out that it didn't work with repacks, had to back out that part of the patch.
Build 1
Preparing to start Automation
- Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
- Reserve slaves
[cltbld@buildbot-master34 master]$ echo "6" > /builds/buildbot/build1/master/reserved_slaves
- For build1 only, create a symlink for your $version (eg 11.0b4, 10.0.2esr, 10.0.2, 3.6.27) (until bug 725839 is resolved)
# tbirdbld@stage cd /pub/mozilla.org/thunderbird/nightly/ mkdir ../candidates/14.0b3-candidates ln -s ../candidates/14.0b3-candidates 14.0b3-candidates
- Update l10n changesets & hit "ship it"
wget -O mozilla/l10n-changesets_thunderbird-beta https://l10n.mozilla.org/shipping/l10n-changesets?ms=tb14_beta_b3
- Land automation configs
- Tag buildbot-configs, buildbotcustom, & tools with build & release tags.
- hg tag THUNDERBIRD_14_0b3_{RELEASE,BUILD1}
- update and reconfigure the master
- release sanity dry run
cd /builds/buildbot/build1/master source ../bin/activate PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u coop -V 14.0b3 \ --branch comm-beta --build-number 1 \ --release-config release-thunderbird-comm-beta.py --products thunderbird \ --dryrun -m -l localhost:9001
- start automation
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u coop -V 14.0b3 \ --branch comm-beta --build-number 1 \ --release-config release-thunderbird-comm-beta.py --products thunderbird \ -m -l localhost:9001
- monitor progress on buildbot, i.e. release-comm-beta
Check that the builds are taken after tagging
- done
Branches glog
- Check that tagging created the branches and document them
http://hg.mozilla.org/releases/mozilla-beta/graph/96128 http://hg.mozilla.org/releases/comm-beta/graph/11884
E-mail Metrics
Use the address "metrics-alerts < AT > mozilla < PERIOD > org". Note for first-time-releasers: your email will get held for moderator approval - that is expected. If it happens more than once, get help on #metrics.
Thunderbird,thunderbird,thunderbird,14.0b3,14.0
l10n repacks
- all repacks failed
- bhearsum did the following:
- Repacks failed because bug 757798 added an invalid path to hgtool.py. This patch was double landed (default + production branch) as a fix, and I moved the THUNDERBIRD_14_0b3_{RELEASE,BUILD1} tags to pick it up.
- After that, the repacks got further along but kept failing because they were trying to update the mozilla-beta repo to 'releases/comm-beta'. It became apparent at that point that hgtool.py was never known to work with repacks, so I backed it out for l10n with this patch.
- bhearsum did the following:
Reset reserved slaves
[cltbld@buildbot-master34 master]$ echo "0" > /builds/buildbot/build1/master/reserved_slaves
Going to Beta
Run backupsnip
# tbirdbld@aus3-staging ~/bin/backupsnip Thunderbird-14.0b3-build1
Push to beta
# tbirdbld@aus3-staging ~/bin/pushsnip Thunderbird-14.0b3-build1