Display current try server queue

RESOLVED FIXED

Status

P2
normal
RESOLVED FIXED
11 years ago
5 years ago

People

(Reporter: Waldo, Assigned: nthomas)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
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
(Assignee)

Comment 3

9 years ago
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
(Assignee)

Comment 5

9 years ago
I'll take a look at adapting what I have for pm01/02.
Assignee: nobody → nrthomas
Priority: P3 → P2
(Assignee)

Updated

9 years ago
Depends on: 551789
(Assignee)

Updated

9 years ago
Priority: P2 → P3
Whiteboard: waiting on blocker
(Assignee)

Comment 6

8 years ago
http://build.mozilla.org/builds/pending/try.html
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Priority: P3 → P2
Resolution: --- → FIXED
Whiteboard: waiting on blocker
(Assignee)

Comment 7

8 years ago
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.