Confirmed users
4,293
edits
Line 199: | Line 199: | ||
hg clone http://hg.mozilla.org/build/tools | hg clone http://hg.mozilla.org/build/tools | ||
cd tools/release/updates | cd tools/release/updates | ||
cat moz19-firefox- | cat moz19-firefox-{win32,mac,linux}.cfg | grep -v major | sed 's/betatest/releasetest/' > update.cfg | ||
./verify.sh -t update.cfg 2>&1 | tee quickVerify.log | ./verify.sh -t update.cfg 2>&1 | tee quickVerify.log | ||
Look for any HTTP error codes besides 200 ("OK") and 302 ("Found"): | |||
grep HTTP quickVerify.log | grep -v 200 | grep -v 302 | grep HTTP quickVerify.log | grep -v 200 | grep -v 302 | ||
* kyoto-mz-dl.sinet.ad.jp was stuck, got it taken out of the rotation by pinging IT | |||
* mozilla.securedservers.com had two 404s, was fully synced up when I tested manually | |||
Repeat for major update files | |||
cat moz19-firefox-{win32,mac,linux}-major.cfg | grep -v major | sed 's/betatest/releasetest/' > update-mu.cfg | |||
./verify.sh -t update-mu.cfg 2>&1 | tee quickVerify-MU.log | |||
Before pushing final updates, verify that "release" and "releasetest" channel match: | |||
# on aus2-staging | # on aus2-staging | ||
cd /opt/aus2/snippets/staging/20091222-Firefox-3.0.17 | cd /opt/aus2/snippets/staging/20091222-Firefox-3.0.17 |