Currently we have these builders dominating the input to the MozillaRelease tree, * linux_dep_build * macosx_dep_build * win32_dep_build * macosx_shark_build The first three are from 1.8 builds done under buildbot, the shark one is 1.9. I don't know why we duplicate the output here, and reed is trying to save disk usage on the tinderbox server, so we should consider turning it off.
Looks like TinderboxMailNotifier supports passing a list of builders or categories.
Component: Release Engineering → Release Engineering: Future
Priority: -- → P3
Mass move of bugs from Release Engineering:Future -> Release Engineering. See http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
We're getting these builds there at the moment: * Firefox cvs-1.9.0 linux-i686 * Firefox cvs-1.9.0 mac * Firefox cvs-1.9.0 win32 * tb-linux_dep_build * tb-macosx_dep_build * tb-win32_dep_build This tree was originally intended for Bootstrap-based releases, which are infrequent now, so this is harmless.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.