As a follow-up from bug 1137060, we have ship-able stuff (in this case, the xulrunner package) that is hidden on treeherder, and we have no way to test it on try. So when I accidentally break it, I have no way of knowing, and no reasonable way to verify a fix. If we care about xulrunner packages, the builds need to be shown by default and have a try option to build them. Or if we don't really care about them, let's remove it.
This is a long standing issue for XULRunner and other things that only run on a nightly basis. It's really tough to make the argument that XULRunner should be built on-change solely because of the policy decision that we have to hide nightly-only jobs on TBPL.
The traditional response has always been "what we want is bug 672509 period, no other changes, no other anything in the meantime."
And irrespective of whether we decide to make nightly-only jobs visible, the owner of xulrunner has always said that tier 2, non-visible, is how he wants it.
(In reply to Phil Ringnalda (:philor) from comment #3) > And irrespective of whether we decide to make nightly-only jobs visible, the > owner of xulrunner has always said that tier 2, non-visible, is how he wants > it. Except that XULRunner is a deliverable that we ship with releases. Which means it more or less blocks releases.
Let's please just drive bug 672509 (maybe via bug 961936) and stop them altogether. Nobody wants to maintain XULRunner.
(In reply to Benjamin Smedberg [:bsmedberg] from comment #5) > Let's please just drive bug 672509 (maybe via bug 961936) and stop them > altogether. Nobody wants to maintain XULRunner. Then someone on the Mozilla side needs to work with WeirdAl to make things happen. He keeps trying, but nothing seems to move. And he's busy with side stuff. It seems like this is a "no one wants to do it but it has to be done" thing.
We're killing XULRunner builds in https://bugzilla.mozilla.org/show_bug.cgi?id=1147577, thus WONTFIX.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.