[Buildbot-devel] getting buildslaves to exit after one build?

[Tom Prince]

Dan Kegel <dank at kegel.com> writes:

> As I explained at the start of the thread, I think need to use plain old slaves.

> Latent slaves run on the master,

as does the code snippet you posted

> and use libvirt to set up slaves, but libvirt's lxc support seems iffy.

The LibVirtSlave does, but that is only one implementation of a latent slave.

> I could hack something together based on abstract latent build slaves,
> but my two-line hack seems sufficient.  Is there something particularly
> bad about it?

Other than the fact that it require patching buildbot, where as adding a
new latent slave type doesn't? Having to patch buildbot like that will
make it harder to upgrade.

I know mozilla has some code that does something similiar, but they are
stuck on 0.8.2.

I think it is probably a reasonable use case (where you want to stop the
slave automatically, but it will come up on its own). I suspect that an
empty start_instance, and the stop_instance I posted will likely do the
right thing (more or less). ... Actually, it looks like the code will
reject latent slaves that try connecting when they haven't been asked
to, so this becomes slightly more complicated.

  Tom