I think we need to update Data.js for this, but I'm not sure how. These are currently showing up as N1 through N5... is that normal?
Them being hidden was normal, but apparently someone decided to unhide them.
Ah, no, I just turned them on today. If hiding them is the normal course of action, that's fine.
Hid the m-c android nightly l10n repacks. android-xul will show up at some point (when bug 717522 is fixed) as well as mozilla-aurora.
Looks like the true normal course of action (by which, I mean "repacks for desktop Firefox") is to put them in builds-4hr.js with a totally whacked out revision property, so there's no way they'll ever show up on any tbpl present or future. The one I'm looking at has a l10n_revision that works for being what might have been pulled, a fx_revision that's probably the Firefox that was repacked, and revision set to two revs back from the l10n_revision, in the middle of a push. Dunno what's up with that, but you could match it for mobile by just setting revision to a random uuid :)
I can see how one would one want to not show 100 l10n builds, but given it's 5, why should they be hidden?
If they're shown, a) They should not show up as N1-5, as it seems like nightly compilations are failing. b) These would be the only l10n jobs showing on tbpl for each branch afaik. Developers use tbpl to see when compilation or tests fail, so ideally these would show in a different context (different pages?) c) We should resolve the no-log-uploading (which should be resolved anyway). Right now developers might think that Android nightlies are failing compilation if they're unhidden, which isn't a good thing.