>
> But are there already established techniques for the full exploitation of
>> the compute power of slave hosts, whatever the role of Docker?
>>
>
Lightweight containers are a much cheaper way of separating instances (in
> this case, slaves) than full-blown virtualization - but give you more
I'm new to Jenkins and to Docker, so, naturally, I'm attempting use of both
together :)
I've successfully duplicated the Docker-Jenkins CI steps shown at
www.activestate.com/blog/2014/01/using-docker-run-ruby-rspec-ci-jenkins and
I've looked with interest also at the approaches described in the
>
> Anyone using the docker plugin (
>> wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin)?
>>
>> If so, can I address multiple containers on one docker host using the
>> plugin, or is the container-to-docker host relationship one to one?
>>
>
On Tue, Jun 10, 2014 at 5:16 PM, Richard Bywater wrot
Anyone using the docker plugin
(wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin)?
If so, can I address multiple containers on one docker host using the
plugin, or is the container-to-docker host relationship one to one?
I'm confused about what the master-slave relationship is (or should be)