There's no technical reason we shouldn't be pushing to internal mirrors right away once bug 663358 is fixed. Even if we have to do a build2, we have full control over the files, and can overwrite them at will. To do this, the automation will need to learn how to: * bump the /pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude file on stage. * run the already existing push_to_mirrors builder

whiteboard tags, priority set so that this should turn up in searches for the next round of automation improvement bugs.

This is a lot easier for Betas now because we don't need to update the exclude file for them (per bug 674517). If we had a switch for pushing to mirrors automatically or not we could flip it for the mozilla-beta config without worry!

I'm a little twitchy about this if we have to do a build2, as we have no verification the internal mirrors are working properly. Perhaps if we use the releasetest channel for the automated and QA checks, and drop betatest altogether for betas ?

(In reply to Nick Thomas [:nthomas] from comment #3) > I'm a little twitchy about this if we have to do a build2, as we have no > verification the internal mirrors are working properly. Perhaps if we use > the releasetest channel for the automated and QA checks, and drop betatest > altogether for betas ? That sounds sensible. If/when we get to the point where we push major and/or stability releases to internal mirrors we should test releasetest there, too.

Marking as a dupe of bug 620444. We have more details there. BTW, we push betas to the internal mirrors automatically (bug 692504).