If I allow ssh to the slave then I do not need the agent - it will be copied from the master. The tools can mostly also be auto-installed, so that shouldn't be an issue either... Anyway, I will probably roll my own then...
Thanks, Stefan Am Freitag, 30. Mai 2014 03:54:41 UTC+2 schrieb Michael Neale: > > On Friday, May 30, 2014 2:36:45 AM UTC+10, Stefan Wolf wrote: > >> Hi there, >> >> I am trying to use developer machines as Jenkins slaves to relieve our >> build server. I thought a good way would be to use boot2docker (Developer >> Machines = Windows) and docker images for the slaves. I need an Oracle JDK >> 7 and an nfs-client installed on the slave. >> Searching the docker index yields quite an amount of jenkins slave >> images. Since the acceptance test harness seems to use docker, too, I >> wanted to know if there are some "official" docker images to use as jenkins >> slaves. Or if there are already some best practices regarding the use of >> docker containers as jenkins slaves. >> >> Thanks, >> Stefan >> > > Given a slave means both the agent plus all the bits you want for your > build - would be hard to be totally generic, right? or would your build > steps install things as needed inside a container based on this? (maybe I > misunderstand). > > Note it is possible to have docker in docker - so you could have a generic > slave container connect to the master, but the build step actually start a > build specific container inside the slave (and then bind mount in the > workspace, run the build in that environment). > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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.
