Closed Bug 450988 Opened 17 years ago Closed 16 years ago

Sort builds on tinderbox so that talos builds are towards the left

Categories

(Release Engineering :: General, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: bzbarsky, Unassigned)

Details

It looks like tinderbox sorts builds in alphabetical order. It would be nice to either change that, or change the build names, such that all the talos builds come before all the other builds. The reason for this would be that all the other builds will turn orange on test failure (including the Rlk test, now!), but one has to explicitly watch the set of numbers talos outputs. So it would be good if this were doable without having to scroll all over the place in the horizontal direction, while looking for the right builds in the vertical direction. If they were all flush left, just making the window wide enough for those several builds and scrolling down would work. This would help a lot with catching Tp regressions as they happen, not days later.
Assignee: nobody → server-ops
Component: Tinderbox → Server Operations: Tinderbox Maintenance
Product: Webtools → mozilla.org
QA Contact: tinderbox → mrz
Version: Trunk → other
Assignee: server-ops → nobody
Component: Server Operations: Tinderbox Maintenance → Release Engineering
QA Contact: mrz → release
Can you get buyin from others in dev.planning before we start down this path? Some others might prefer the builds to be sorted to the left.
Component: Release Engineering → Release Engineering: Future
There seem to be no objections (or comments of any sort, other than suggestions for how to work around things pending this change).
Sounds like it's not an issue since we've got tbpl now.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.