When we reach the updates builder we have to remember to have downloaded manually into staging-stage the previous release for this to work. https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Documentation#Staging_specific_preparation

Updating summary to be more generic/include preproduction.

Adds a staging scheduler which is supposed to be fired by release_sanity.py as repo_setup. releaseConfig['skip_release_download'] = True disables the builder (makes it dummy).

* Very similar to push-to-mirrors scripts (a lot of boilerplate :( ) * --download-current-release is supposed to be used in pre-production in the future to download both, prev and current, releases to run update tests (see bug 627667) * Please check the directories to be ignored by -X (-R works for the file part of a URL only, -X requires full prefix). According to the docs in comment #1 we want to ignore at least unsigned directory. I also added contrib*, partner-repacks and win32-EUBallot. * Staging tests are passed :)

Comment on attachment 509024 [details] [diff] [review] release_downloader scripts This wget looks fine in the "downloading the previous release" for now, but if we ever want to download the current release for the purpose of comparing a re-run of it, we'll be wanting everything except unsigned. You're cd's before clobberer and purge_builds go one too far: adjust them like this: http://hg.mozilla.org/build/tools/file/tip/scripts/l10n/release_repacks.sh#l37, lest we have a repeat of broken Scratchboxes.

Comment on attachment 509024 [details] [diff] [review] release_downloader scripts http://hg.mozilla.org/build/tools/rev/efbae13b5be3

Comment on attachment 509022 [details] [diff] [review] buildbotcustom part http://hg.mozilla.org/build/buildbotcustom/rev/4099ebfd1831

Merged/deployed: http://hg.mozilla.org/build/buildbotcustom/rev/0f730cd0cffc