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, Gallagher Polyn <[email protected]>
wrote:

> 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 two
> additional Docker-CI references, farther below.
>
> Writers on Docker-CI assert that the lightweight nature of Docker
> containers allow faster testing, because Docker test environments can very
> easily be created, modified and reused by the CI server.
>
> 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 slave host
> and not sequentially.
>
> But are there already established techniques for the full exploitation of
> the compute power of slave hosts, whatever the role of Docker?
>
> Thanks, G
>
>
> http://developer.rackspace.com/blog/move-fast-and-dont-break-things-testing-with-jenkins-ansible-and-docker.html
>
> http://www.ebaytechblog.com/2014/05/12/delivering-ebays-ci-solution-with-apache-mesos-part-ii/#.U5d-VJRdXCd
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to