[users at bb.net] Running builds in a new machine instance every time

[Damiano Boppart]

Hi,

I would like to know what the most elegant way is for running builds
with buildbot when I need to set up the environment that is used for
building anew every time. Since my application is built on different
OS's the setup of the build environment is also different:

* For Linux builds, I want to create a new LXC container, and build in that.
* For Windows, I want to restore to a snapshot of a Virtualbox VM image,
and build in that.
* For macOS, I want to delete and re-create a user account on an
always-running machine, and build as that user.

Now, it is my understanding that a buildbot worker (except for latent
workers) is expected to run exactly where the build is performed (inside
the LXC container, on the windows VM, or under the user account for
builds in my 3 scenarios).

As the place where the build takes place is only created for a build,
the worker thus can't be always running.

In the case of Linux/LXC, I can use the libvirt latent worker to
implement what I want, but how can I do this for the other two platforms?

Can I run the Windows/macOS worker "outside" of the place where I
actually execute my build?

Yours,

Damiano