Releases/Firefox 2.0.0.16-3.0.1 MU:BuildNotes: Difference between revisions

Releases/Firefox 2.0.0.16-3.0.1 MU:BuildNotes (view source)

973 bytes added , 21 August 2008

no edit summary

canmove, Confirmed users

6,440

edits

@@ Line 114: / Line 114: @@
   ~/bin/backupsnip 20080820-Firefox-2.0.0.16-3.0.1-MU-test
   ~/bin/pushsnip 20080820-Firefox-2.0.0.16-3.0.1-MU-test
+= Fix up null partner snippets to target 2.0.0.14 =
+After partner snippets were pushed I was informed that the latest partner builds we shipped were for 2.0.0.14. Therefore, the snippets pushed are useless. To fix them up, did the following:
+ # cltbld@aus2-staging.mozilla.org
+ cd ~/
+ rsync -av /opt/aus2/snippets/staging/20080820-Firefox-2.0.0.16-3.0.1-MU-null 20080821-Firefox-2.0.0.14-null-partner-snippets
+ cd 20080821-Firefox-2.0.0.14-null-partner-snippets/Firefox
+ mv 2.0.0.16 2.0.0.14
+ # using mv because rsync takes ~1h to complete, no need to keep these in the homedir anyways
+ mv 20080821-Firefox-2.0.0.14-null-partner-snippets /opt/aus2/snippets/staging
+ # re-backup & push
+ # had to delete staging directory for bad snippets to back space for backup
+ cd /opt/aus2/snippets/staging
+ rm -rf 20080820-Firefox-2.0.0.16-3.0.1-MU-null/
+ ~/bin/backupsnip 20080821-Firefox-2.0.0.14-null-partner-snippets
+ ~/bin/pushsnip 20080821-Firefox-2.0.0.14-null-partner-snippets
 = Verify null partner updates =
@@ Line 119: / Line 135: @@
   ./create_aus_urls.sh
 Used test_null_updates.sh to test all snippets:
-  ./test_null_updates.sh mu-2.0.0.16-3.0.1-null-urls.txt 2>&1 | tee before.log
+  ./test_null_updates.sh mu-2.0.0.14-3.0.1-null-urls.txt 2>&1 | tee before.log
   # grep the log for any non-passes
   grep -v '^PASS'