[Buildbot] #2956: Provide latent Docker build slave
Buildbot trac
trac at buildbot.net
Tue Oct 28 10:58:02 UTC 2014
#2956: Provide latent Docker build slave
----------------------------------+--------------------
Reporter: sa2ajj | Owner:
Type: enhancement | Status: new
Priority: patches-accepted | Milestone: 0.9.+
Version: master | Resolution:
Keywords: docker, slave, latent |
----------------------------------+--------------------
Comment (by sa2ajj):
Replying to [comment:6 Ben]:
> I started looking onto it, unfortunately, I hit a few blockers with
master (#2970).
Let's see how it's resolved.
> A question I had is about the completness of the docker image.
> Should we try to create-slave + start at each substiantiation ?
> Or should the image have a pre-created slave and it should only be
started during substantiation ?.
I think the best is make all latent build slaves behave in a similar way;
this means that it's a responsibility of the user to create an image with
build slave in it as well as to provide a way for the build slave to
authenticate against master:
* some latent build slaves have this information "hardcoded", that's it:
one image can only provide one build slave
* majority of images I saw use environment variables or a bootstrap script
to configure the authentication
> In other words: Should the docker image be buildbot-aware, or should any
(well, with limitations) docker image be made buildbot-aware ?
I think, the former: that's in line with, for example, AWS images.
--
Ticket URL: <http://trac.buildbot.net/ticket/2956#comment:7>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
More information about the bugs
mailing list