[Buildroot] autobuild statistics graph

[Arnout Vandecappelle <arnout@mind.be>]

On 08/29/13 10:40, Thomas De Schampheleire wrote:
> Hi Thomas,
>
> On Thu, Aug 29, 2013 at 10:15 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>
>>
>> Another great thing would be to draw some thin vertical lines at the
>> dates of the various releases (-rc1, -rc2, final and so on), so we can
>> see if the rate of failures/success correlate with releases or not.
>> It'd be fun, but I'm not sure it's really worth the effort because
>> besides the releases themselves, another major thing causes big
>> variations in the rate of success/failure: when I had a new toolchain
>> for a new architecture, or a new configuration type (eg. static
>> builds). I believe those changes in the configuration of the
>> autobuilders are causing more variations in the results than the
>> release cycles themselves.
>>
>
> Yes, I also considered that having the releases indicated in the graph
> would be interesting. In fact, if we'd have these big moments shown in
> the graph, the actual dates wouldn't really matter anymore and could
> be hidden completely IMO.
>
> If you still have the info about when some of the big changes (like
> new toolchain etc.) was done, we can definitely put that alongside the
> release milestones.
>
> How to best store the milestones (in the database or in the graph.php
> file itself), I'm not sure. They'll probably need to be manually
> updated, but that could be done both in the database as in graph.php.
> How to show these milestones in the graph is also not entirely clear.
> I can't find a way to pass some custom x values to  pChart. One
> solution is to manipulate the date array from php before passing it to
> pChart. This way, if we have a map between date (as it appears in the
> database) and event, we can replace the dates by the events, and make
> all other strings empty. This should give the desired result I think.

  Ideally the horizontal axis should be based on git commit IDs instead 
of build date, and the labels could be the tags.  And you could manually 
add tags to the clone from which the commit IDs are extracted to indicate 
those interesting points where toolchains are added etc. But that would 
be a bit too much effort I guess :-)

  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F