Confirmed users
2,679
edits
Firefox 3.0b4:BuildNotes: Difference between revisions
→Updates to Test Channel
| (9 intermediate revisions by the same user not shown) | |||
| Line 156: | Line 156: | ||
* fallout from [https://bugzilla.mozilla.org/show_bug.cgi?id=410006 bug 410006] (prettyVersion feature); AUS dir "3 Beta 3" is created, not "3.0b3". | * fallout from [https://bugzilla.mozilla.org/show_bug.cgi?id=410006 bug 410006] (prettyVersion feature); AUS dir "3 Beta 3" is created, not "3.0b3". | ||
** workaround patch in [https://bugzilla.mozilla.org/show_bug.cgi?id=418926 bug 418926], re-gen and re-push AUS config | ** workaround [https://bugzilla.mozilla.org/attachment.cgi?id=301534&action=edit patch] in [https://bugzilla.mozilla.org/show_bug.cgi?id=418926 bug 418926], re-gen and re-push AUS config | ||
** FIXME permanent fix in [https://bugzilla.mozilla.org/show_bug.cgi?id=420947 bug 420947] | ** FIXME permanent fix in [https://bugzilla.mozilla.org/show_bug.cgi?id=420947 bug 420947] | ||
| Line 394: | Line 394: | ||
rsync -av /data/cltbld/firefox-3.0b4/stage-merged/ /home/ftp/pub/firefox/releases/3.0b4/ | rsync -av /data/cltbld/firefox-3.0b4/stage-merged/ /home/ftp/pub/firefox/releases/3.0b4/ | ||
* TODO: note that in /data/cltbld, the "firefox-3.0b4" directory should probably be "firefox-3.0b4rc2". This would make it easier to confirm changes between RCs. This is done for some releases not all; should we always do this? | * TODO: note that in /data/cltbld, the "firefox-3.0b4" directory should probably be "firefox-3.0b4rc2". This would make it easier to confirm changes between RCs. This is done for some releases not all; should we always do this? | ||
====Updates to Beta Channel==== | |||
'''In case you need to cancel/abort updates, the quickest way to do this is [https://intranet.mozilla.org/Build:Farm:Tinderbox_Maintenance#Starting.2FStopping_Tinderbox_on_win32]''' | |||
* on Mac build machines, run quick updateverify test for releastest channel | |||
cd /builds/verify/firefox-3.0b4/updates | |||
cat moz19-firefox-*.cfg > releasetest.cfg | |||
sed -i.bak 's/betatest/releasetest/' releasetest.cfg | |||
./verify.sh -t releasetest.cfg 2>&1 | tee releasetest.log | |||
# upload result to build.m.o/logs | |||
Should be all HTTP/200 OK results e.g.: | |||
grep 'HTTP' releasetest.log | grep -v Found | grep -v 200 | |||
* On aus2-staging, ensure that releasetest channel contents match beta channel contents | |||
cd /opt/aus2/snippets/staging/20080308-Firefox-3.0b4 | |||
find -type d -iregex '.*beta.*' | perl -nle '$a = $_; $a =~ s/beta/releasetest/; system("diff -r -u $_ ../20080308-Firefox-3.0b4-test/$a");' | |||
No difs found - which is correct. | |||
* Once QA and Website gives formal "go" | |||
# put snippets on beta | |||
# login to aus2-staging | |||
$ sudo su - cltbld | |||
$ cd /opt/aus2/snippets/staging | |||
$ ~/bin/pushsnip 20080308-Firefox-3.0b4 | |||
* on Mac build machines, run quick updateverify test for beta channel | |||
cd /builds/verify/firefox-3.0b4/updates | |||
cat moz19-firefox-*.cfg > beta.cfg | |||
sed -i.bak 's/betatest/beta/' beta.cfg | |||
./verify.sh -t beta.cfg 2>&1 | tee beta.log | |||
# upload result to build.m.o/logs | |||
Should be all HTTP/200 OK results e.g.: | |||
grep 'HTTP' releasetest.log | grep -v Found | grep -v 200 | |||
== Wall clock timings == | == Wall clock timings == | ||
== Stopping live updates (just in case!) == | |||
If QA finds a problem with updates *after* we start pushing updates "live", the one-and-only-one way we know to stop updates from further spreading is by killing all updates! | |||
See instructions at: https://intranet.mozilla.org/Build:Updates . | |||