No subject

http://roberthelmer.com/blog/?p=23

Grig

--- Grig Gheorghiu <grig at gheorghiu.net> wrote:

> --- Michael Stone <michael at laptop.org> wrote:
> 
> > Grig,
> > 
> > I spent this afternoon reading through the buildbot manual and it
> > looks
> > like it might be adaptable to the shape of my needs. Here's how I
> > intend
> > to begin:
> > 
> > 1) Since I expect rapid growth in the quantity and diversity of
> >    measurements being made and configurations being analyzed, an
> >    architecture like that of pybots seems appropriate. Therefore,
> I'd
> >    like to set up just the minimal buildbot configuration required
> to
> >    distribute the checking of exactly two assertions in response to
> >    build completion. 
> > 
> >    In the future, I'll be happy to investigate running our OS image
> >    build tools under buildbot for even better status reporting,
> >    change/failure correlation, and performance.
> 
> 
> Sure -- ideally we'd need 2 machines to start with: one to act as the
> buildbot master, and one to act as a buildbot slave. Let me know if
> you
> have them, or if we need to ask for volunteers to run them.
> 
> > 
> > 2) The assertions I want to check are that 
> > 
> >    * /home/olpc is owned by olpc/olpc with mode 0775 
> >    * /usr/share/activities/*/build_index.html is writable by group
> > olpc
> > 
> >    These properties can be checked directly on the filesystem
> > tarball;
> >    no fancy setup, teardown, or environment is necessary to collect
> > or
> >    to interpret the results.
> > 
> >    In the future, I will clearly want to check properties that are
> >    harder to measure. 
> 
> This should be easy to achieve.
> 
> > 
> > 3) Once I get this far, it will hopefully be obvious how to proceed
> >    further.
> > 
> 
> I hope so too.
> 
> Grig
>