> > > > 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? > > > Not sure I understand the question. Running slaves on docker is no more special than running them on other cloud based services; it has the advantage that it's particularly cheap and fast to spin up slaves on demand, and there is a nice infrastructure around sharing containers around.
There's nothing there that hasn't been available in, say, Solaris Zones for many years - it's mostly that docker has helped polish lxc (the underlying technology), generated a nice API and really helped it gain traction. Lightweight containers are a much cheaper way of separating instances (in this case, slaves) than full-blown virtualization - but give you more separation than simply running multiple build jobs on one slave computer. -- 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.
