ReleaseEngineering/How To/Generate partial updates: Difference between revisions

ReleaseEngineering/How To/Generate partial updates (view source)

996 bytes added , 12 July 2012

Confirmed users

4,293

edits

@@ Line 173: / Line 173: @@
 = Push to mirrors =
+If you haven't released yet there isn't anything to do here, because everything will get pushed by the automation when the go comes. If the release has shipped already you need to push the new partials out.
+From a build slave:
+ ssh -oIdentityFile=~/.ssh/ffxbld_dsa ffxbld@stage.mozilla.org
+ rsync -nav --exclude=*tests* --exclude=*crashreporter* --exclude=*.log --exclude=*.txt --exclude=*unsigned* \
+  --exclude=*update-backup* --exclude=*partner-repacks* --exclude=*.checksums --exclude=*.checksums.asc \
+  --exclude=logs --exclude=jsshell* --exclude=*.zip --exclude=*.zip.asc --exclude=contrib* \
+  /pub/mozilla.org/firefox/nightly/$NEWV-candidates/build$BUILD/ /pub/mozilla.org/firefox/releases/$NEWV/
+Verify the list is correct - expect the new partial.mar's + asc files, the SUMS files and their asc's, and the directories containing them.
+Then remove the n from -nav to push for real. This should take < 15 min to copy; allow 3 hours for mirror a reasonable number of mirrors to sync.
 = Final verification =
 = Pushsnip =