>
> 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
>
>
>
> My question is whether Docker's lightweight nature also allows better
> exploitation of Jenkins' master-slave paradigm. Under this, I might expect
> that several Docker slaves on some slave Docker host could run in parallel.
> Thus, test suites would be broken down and run in parallel on a
Sorry, ignore my previous reply - I didn't realise that you were already
using the Docker Plugin and that we'd already communicated in another
thread. Presumably you are looking for more of a discussion around usage of
Docker & Jenkins in general :)
Richard.
On Thu, Jun 12, 2014 at 6:28 AM, Gall
On my phone so can't check those links fully yet but you probably want to
give the Jenkins Docker plugin a go. This exposes Docker as a cloud slave
provider so you can dynamically spin up a slave of a particular flavour to
run your job on.
HTH
Richard
On Thursday, June 12, 2014, Gallagher Polyn
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
