[Buildbot-devel] repo and gerrit support to buildbot

[Marc-Antoine Ruel]

Le 28 septembre 2010 12:04, tom fogal <tfogal at sci.utah.edu> a écrit :

> Pierre Tardy wrote:
> > The test part might be a bit trickier. It is not possible to run the
> > test on the same machine as the build.
> > Build machines are typically big virtualised servers, and test machine
> > are not very power powerful lab machines hooked up to lab equipment
> > and targetted hardware.
>
> Given that you're using virtualized servers, you might want to look into
> latent build slaves.  I talked to someone on IRC who was launching a
> guest OS, which started buildbot, did a build, and then shutdown the guest.
>
> > Do you think it possible to use a status object to trigger a change
> > event, that can trigger a builder which is actually only tester
> > (download result of build and run tests on embedded hw)
>
> I run tests as part of both buildbots I manage.
>
> What you want is definitely possible.  Just use a dependent scheduler
> and have the test build[s] depend on the main build.
>

That's what we also do in chromium. It's all documented. We seeds a ton of
'testers' builders with our 'builders' builders. I love nomenclature.

If you need to move code from the builder to the tester, use a
> FileUpload at the end of the build factory, and a FileDownload at the
> beginning of the test factory.
>

We use a local web server on our slaves because FileUpload/Download isn't
efficient for multi-gigs files.



> You shouldn't need to change buildbot at all for this, it can all be
> done in your configuration[s].
>
> HTH,
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20100928/ce6b8331/attachment.html>