[Buildbot-devel] Storing compile/test results in a database?

[Kristian Nielsen]

Kristian Nielsen <knielsen at knielsen-hq.org> writes:

> I know that it has already been discussed to use an SQL database for backend
> storage of Buildbot state and history, and that the idea is for this to go in
> 1.0. However, I have a need to get some data in a database now, and my needs
> are also somewhat different, so I wanted to bounce off some ideas and hear if
> there is already some existing effort that I could build on.

> Basically I want to store every test case failure in a database along with
> information about branch, revision, error output, etc. This will allow to
> easily create additional webpages, a facility to search for previous failures
> across different builds, etc. (At MySQL AB I wrote an internal tool for this,
> and the database was > 1 GB in size).

In case anyone is interested in what came of this, I implemented it, and it
works fine. It is running here:

    http://askmonty.org/buildbot/

For an example of the additional information available on the waterfall page,
see for example here:

    http://askmonty.org/buildbot/waterfall?branch=5.1&show_events=false

For an example of using the stuff in the database, see eg. here:

    http://askmonty.org/buildbot/reports/cross_reference#branch=mariadb-xtradb-merge2&revision=2717&platform=jaunty-x86-valgrind&dt=&bbnum=&typ=&info=&fail_name=&fail_variant=&fail_info_short=&fail_info_full=

The code is available here:

    http://github.com/knielsen/buildbot/tree/mtrlogobserver

(I have proposed it for merging upstream).

 - Kristian.