Re: ideas for auto-processing patches

On 1/4/07, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> Gavin Sherry wrote:
> > On Thu, 4 Jan 2007 markwkm(at)gmail(dot)com wrote:
> >
> >> 1. Pull source directly from repositories (cvs, git, etc.) PLM
> >> doesn't really track actually scm repositories. It requires
> >> directories of source code to be traversed, which are set up by
> >> creating mirrors.
> >
> > It seems to me that a better approach might be to mirror the CVS repo --
> > or at least make that an option -- and pull the sources locally. Having to
> > pull down >100MB of data for every build might be onerous to some build
> > farm members.
> >
>
>
> I am not clear about what is being proposed. Currently buildfarm syncs
> against (or pulls a fresh copy from, depending on configuration) either
> the main anoncvs repo or a mirror (which you can get using cvsup or rsync,
> among other mechanisms). I can imagine a mechanism in which we pull
> certain patches from a patch server (maybe using an RSS feed, or a SOAP
> call?) which could be applied before the run. I wouldn't want to couple
> things much more closely than that.

I'm thinking that a SOAP call might be easier to implement? The RSS
feed seems like it would be more interesting as I am imagining that a
buildfarm system might be able to react to new patches being added to
the system. But maybe that's a trivial thing for either SOAP or an
RSS feed.

> The patches would need to be vetted first, or no sane buildfarm owner will
> want to use them.

Perhaps as a first go it can pull any patch that can be applied
without errors? The list of patches to test can be eventually
restricted by name and who submitted them.

Regards,
Mark