[Buildbot-devel] SQL question

[Axel Hecht]

I have a (django based) tree with some db work, too. That's really
focussing only on the status for now, as that is what I needed, for
two reasons:

Being able to do more build-spanning queries (all builds with a
particular property, in particular) is one, the other one is to get
the status output out of the master into a separate process.

Dustin, I'm not sure if the persistance of process objects really
needs to be in a db, any data in particular that you had in mind? I
wonder if doing mixed pickles (hahaha) is good enough, status in a db,
process persistance in pickles.

Axel

2008/6/19 Charles Lepple <clepple at gmail.com>:
> On Thu, Jun 19, 2008 at 4:13 PM, Mark MacVicar <mark.macvicar at gmail.com> wrote:
>> I saw this item in the Buildbot Trac system
>> http://buildbot.net/trac/ticket/24. Has anyone played around with
>> storing build results into a database?
>
> As I alluded to in the metrics thread, I have some homegrown
> subclasses of standard build rules that store information gleaned from
> a given build.
>
> Since I was only concerned with storing the results from complete
> builds, this saves me an extra SELECT on the database because Buildbot
> will only get to the database step if the other build steps complete.
>
> I used Django, so I created a model for representing successful
> builds, and stored things like the branch, revision, builder, download
> URL, etc. into the build object before saving it.
>
> --
> - Charles Lepple
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>