[Buildbot-devel] (no subject)

[Dustin J. Mitchell]

On Tue, Jan 31, 2012 at 9:20 PM, Dmitry Mikhin <dmitry.mikhin at gmail.com> wrote:
> I have a builder oriented towards measuring application performance (run
> time) for a set of inputs. The purpose is to prevent unintended side effects
> on performance when source changes occur. The build system runs these tasks
> and reports timing in the log. Subclassing ShellCommand and providing a
> custom createSummary method I extract those values. So far so good.

This sounds like what Mozilla calls "Talos" - that may be an
interesting avenue for exploration.

> - how and where can I store the obtained measurement within the buildbot
> system. Should I use Properties? Something else? For each run I need to
> store the time readings for multiple input files, and later compare with the
> earlier builds. How can I fetch the old values?

This is generally best stored outside of buildbot.

> - Once I have the timing values, those have to be presented in a new page
> linked from WebStatus (now a nearly-empty page added via putChild call),
> ideally as lots "run-time vs. revision Id (or calendar time)". Hopefully I'm
> not the first one attempting to produce such a display. Can anyone recommend
> a working example?
>
> I'm new to buildbot (although reasonably proficient in Python), my apologies
> if this topic is covered somewhere in the manual or wiki.

It's not -- this is a use of Buildbot that's not well-supported right now.

Dustin