Closed Bug 414081 Opened 17 years ago Closed 14 years ago

Display current try server queue

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Waldo, Assigned: nthomas)

References

Details

There's no way to know how long it'll be before you have builds unless there's no backup, which is inconvenient.
Mass change of target milestone.
Target Milestone: --- → Future
Component: Try Server → Release Engineering
Product: Webtools → mozilla.org
QA Contact: try-server → release
Target Milestone: Future → ---
Version: Trunk → other
This is wanted for production-master as well.
Futuring until we have resources to put on this.
Component: Release Engineering → Release Engineering: Future
The best way to do this will be as a frontend to the buildbot database (bug 488273).
Depends on: 488273
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
I'll take a look at adapting what I have for pm01/02.
Assignee: nobody → nrthomas
Priority: P3 → P2
Depends on: 551789
Priority: P2 → P3
Whiteboard: waiting on blocker
http://build.mozilla.org/builds/pending/try.html
Status: NEW → RESOLVED
Closed: 14 years ago
Priority: P3 → P2
Resolution: --- → FIXED
Whiteboard: waiting on blocker
Resolved without the status db (bug 488273). We can do a better job once the scheduler db and buildbot 0.8.0 are deployed, and it'll need redoing once try-as-a-branch lands.
No longer depends on: 488273
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.