Release:Release Automation on Mercurial:Troubleshooting: Difference between revisions

Jump to navigation Jump to search

Release:Release Automation on Mercurial:Troubleshooting (view source)

Revision as of 20:50, 23 January 2013

63 bytes removed ,  23 January 2013
→‎I pushed the wrong files to releases/, help!
No edit summary
Line 73: Line 73:
Known issue: rsync will reset the permissions from 700 to 755.  You will need to set them back to 700 if you want to continue to not allow AUS updates.
Known issue: rsync will reset the permissions from 700 to 755.  You will need to set them back to 700 if you want to continue to not allow AUS updates.


=== I pushed the wrong files to releases/, help! ===
=== Overwriting files that have been pushed to releases/ ===
Overwriting files after they've been pushed here isn't safe to do. We can't guarantee that 3rd party mirrors will pick them up in a timely manner, and the CDN caches files for 4 days. Because of this we need to push the files to a different directory and make a couple of adjustments to make sure our tests still work and users get the right files. Specifically
If a rebuild happens after an earlier build has been pushed to mirrors already, a few steps need to be taken to make sure that the files can be pushed and that the CDN serves the content. The following should happen before "push to mirrors" runs in the new build. (If you're not in a rush, it's best to do these before kicking off the new release to make sure it does in fact happen in time):
* Delete the affected directory (eg, /pub/mozilla.org/thunderbird/releases/$version)
* Delete the directory from releases. For example:
* Push the correct files to a new directory. The best way to do this is to look at the "push to mirrors" builder of the automation, copy the rsync command, and adjust the target directory to be eg: $version-real instead of $version.
# ffxbld@upload1
* Symlink $version to $version-real. This step ensures that update verify will work.
rm -rf /pub/mozilla.org/firefox/releases/19.0b2
* Update the bouncer entries to point at $version-real. Be sure to update all of the partials (there may be more than one set of them), the completes, and the installer. Ask someone if you're not sure if you've got them all.
* File an IT bug to have the CDN caches purged (eg "please purge the CDN cache for /pub/mozilla.org/firefox/releases/19.0b1"). These should generally be filed as critical or blocker. Definitely file as a blocker if you're under time pressure.
* Run/rerun final verification and ask QA to sanity check.
 
If you don't delete the releases directory prior to "push to mirrors" running you'll end up with that builder and "check permissions" failing. These should be re-run after you delete the existing contents of the directory.
Bhearsum
canmove, Confirmed users
6,441

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/504576"

Navigation menu