[Buildbot-devel] RFC: more flexible web status display

[Brian Warner]

> And while I'm here, I would like if the changes were grouped together
> in the next batch.  Since the tests take an hour + to run, some slaves
> get really far behind.  It would be nice to aggregate outstanding
> changes into a batch even if they didn't arrive within the same five
> minutes.

They should be doing that already. Any changes that arrive after the current
build has started but before the next one starts will be lumped together into
the second build. In the case of SVN, this means that the second build will
be run with something like "-r %d" % max([c.revision for c in changes]) . If
you're seeing behavior that doesn't match this, point me at your Waterfall
and I'll take a look.

If you've got developers who are in the habit of spreading related commits
out over 10 or 15 minutes, and want to improve the chances that their changes
all get put into the same build, you can always crank up the treeStableTimer
(an argument to the Scheduler class). But this comes at the expense of timely
notification of build errors, of course.

cheers,
 -Brian