[Buildbot-devel] Changeset display order in waterfall versus T-Grid

[Iustin Pop]

On Fri, Jul 23, 2010 at 15:33, Dustin J. Mitchell <dustin at zmanda.com> wrote:
> On Fri, Jul 23, 2010 at 1:31 PM, Iustin Pop <iustin at google.com> wrote:
>> Would it make sense to either modify T-Grid to accept a parameter for
>> this, or maybe to reverse the sort order permanently as to match the
>> Waterfall one?
>
> I hate to be the crotchety old man on this issue, but this is a case
> where everyone wants slightly different things.

Of course :)

> The web display configuration is not really amenable to adding
> configuration knobs for every tweak, since they must go in at the
> toplevel (WebStatus constructor).

Hmm, I was thinking something like the Waterfall argument show_events,
which I see as being read in the code of WaterfallStatusResource, and
not being declared in the WebStatus constructor. Do I misread the
code?

> There are lots of projects nipping
> around the edge of this problem - most use some web service API or
> another to extract data from the buildmaster and redisplay it in a
> different form.  I'd prefer to see things develop in this direction,
> instead - eventually, I'd like to see the built-in WebStatus present a
> basic, no-frills (and optional) view of buildbot's activities, with
> one or more official web frontends, perhaps written in Django or
> something like that, able to interface to the master remotely.

That sounds like a good idea, except that it will complicate setting
up buildbot for a small project. But I understand the rationale behind
it…

thanks for the response,
iustin