| Summary: | Easy way to see all individual builds for a build | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Ross Burton <ross.burton> | ||||
| Component: | autobuilder | Assignee: | Unassigned <unassigned> | ||||
| Status: | RESOLVED OBSOLETE | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | Medium | CC: | bluelightning, elizabeth.flanagan, infras.ab.watcher, Infras.watcher, sgw | ||||
| Version: | unspecified | ||||||
| Target Milestone: | Future | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | Was Bill Randle | ||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | Don't know | |||||
| Attachments: |
|
||||||
|
Description
Ross Burton
2013-05-10 08:31:15 UTC
Ross, could you explain a bit more how you want this to work? Which type of view? One bit of utility I could see (and I'll have to investigate how hard it would be) is to be able to see the waterfall of that buildrun by clicking the sha. Created attachment 1533 [details]
Very predictable mockup
I find that sometimes when reviewing several build failures the eg tgrrid view can get a bit wide and its easy to lose track of the row I'm paying attention too.
A waterfall mode would be useful.
An alternative solution would be to nest the table inside a scrolling thingy so the headers are always visible. That would probably be better, tbh.
Whoops, left this in needinfo. I think this is moot now, the new AB code is much easier to work with. |