Improved web status page

[GoogleCodeExporter]

The current waterfall status page is painly confusing if one has a lot of
builders doing a lot of builds that each taking much time (such as
termite.go-oo.org).
I consistently end up in scrolling up and down the page searching for a
specific build. 

There are several other tools that have a better overview/status page (e.g.
http://vmbuild.apache.org).

Perhaps this issue will be obsolet with a new buildbot version.

Original issue reported on code.google.com by [email protected] on 18 Aug 2008 at 12:39

[GoogleCodeExporter]

Original comment by [email protected] on 18 Aug 2008 at 3:08

• Changed state: Started

[GoogleCodeExporter]

Some wishes for the new UI:
- get info about pending builds
- displayed timescale can be changed (e.g. 12/24/50/100 hours)
- clean up page for starting builds (cws/mws name, no branch nonsense)
- continue with status output after ping

- comment on builds/errors
- autoreload (configurable :))
- see in the listing what CWS was built instead of just "Build xx"

Original comment by [email protected] on 19 Aug 2008 at 11:43

[GoogleCodeExporter]

Another wish:
Auto-hide offline/idle builders without logs.

Original comment by [email protected] on 19 Aug 2008 at 11:52

[GoogleCodeExporter]

Some of the things mentioned here are already implemented or on the Buildbot 
Ticket 
list.
Some are still unique:
- Auto-hide offline/idle builders without logs.
- comment on builds/errors
- displayed timescale can be changed (e.g. 12/24/50/100 hours)

Original comment by [email protected] on 17 Sep 2008 at 2:10

[GoogleCodeExporter]

The displayed time interval can be changes using waterfall URL parameters:
"The last_time= argument is a unix timestamp (seconds since the start of 1970) 
that 
will be used as an upper bound on the interval of events displayed: nothing 
will be 
shown that is more recent than the given time. When no argument is provided, 
all 
events up to and including the most recent steps are included.

The first_time= argument provides the lower bound. No events will be displayed 
that 
occurred before this timestamp. Instead of providing first_time=, you can 
provide 
show_time=: in this case, first_time will be set equal to last_time minus 
show_time. 
show_time overrides first_time."
So this point is fixed :-)

Remaining:
- Auto-hide offline/idle builders without logs.
- comment on builds/errors  (Why should that be useful?)

Original comment by [email protected] on 23 Sep 2008 at 2:21