[Buildbot] #3350: Graph in Buildbot

[Buildbot trac]

#3350: Graph in Buildbot
--------------------------+--------------------
Reporter:  stibbons       |       Owner:
    Type:  undecided      |      Status:  new
Priority:  major          |   Milestone:  0.9.+
 Version:  master         |  Resolution:
Keywords:  chart,metrics  |
--------------------------+--------------------
Changes (by sa2ajj):

 * milestone:  undecided => 0.9.+


Old description:

> Produce some key, visual, and useful graphs, that will help users feeling
> confortable with the buildbot we interface.
>
> Examples:
> * A) [https://issues.jenkins-
> ci.org/secure/attachment/24712/TimelineMissingDataWrongHour.jpg Build
> Time]
> * B) [http://i.stack.imgur.com/dMkkN.png Test Result]:
>
> A) is pretty easy to do, and I think the Data API can give us this data
> on the fly (correct me if I am wrong).
>
> B) need to extract data from the step, a given step would exposes the
> number of test success/failed. This would use the Statistic API
> developped this summer 2015.
>
> Plan:
> * A) first step, to integrate the graph framework, connect to real data
> (already in the database).
> * B) I propose the following architecture:
>   - connect the stat service to a new table inside the main buildbot
> database (either mysql, sqlite,...). This would store only test results,
> per build, as an example.
>   - StatService can be configured to feed this table, but it is not
> mandatory
>   - the web interface needs to query (data API?) this table to retrieve
> data for a given builder
>   - the graph is displayed to the user
>
> For graph framework, I really like [http://www.highcharts.com/
> Highcharts] which is free for non commercial use.

New description:

 Produce some key, visual, and useful graphs, that will help users feeling
 confortable with the Buildbot web interface.

 Examples:
 * A) [https://issues.jenkins-
 ci.org/secure/attachment/24712/TimelineMissingDataWrongHour.jpg Build
 Time]
 * B) [http://i.stack.imgur.com/dMkkN.png Test Result]:

 A) is pretty easy to do, and I think the Data API can give us this data on
 the fly (correct me if I am wrong).

 B) need to extract data from the step, a given step would exposes the
 number of test success/failed. This would use the Statistics API
 developped this summer 2015.

 Plan:
 * A) first step, to integrate the graph framework, connect to real data
 (already in the database).
 * B) I propose the following architecture:
   - connect the stat service to a new table inside the main buildbot
 database (either mysql, sqlite,...). This would store only test results,
 per build, as an example.
   - StatService can be configured to feed this table, but it is not
 mandatory
   - the web interface needs to query (data API?) this table to retrieve
 data for a given builder
   - the graph is displayed to the user

 For graph framework, I really like [http://www.highcharts.com/ Highcharts]
 which is free for non commercial use.

--

--
Ticket URL: <http://trac.buildbot.net/ticket/3350#comment:1>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation