> > In the end I couldn't use the Docker Jenkins plugin as there's an issue > with it not creating a new instance of a container if there is already a > job running with the same label (which kind of defeats the point of using > the Docker plugin IMHO) >
So that was certainly something I tested mid to back end of last year when I POCed using docker for slaves, and it worked ok (although there was a small delay before the new slave). If thats the case maybe try rolling back the version - as it is by far the easiest way to go and you don't have to have the containers idling which makes load balancing much easier. On Thursday, 28 May 2015 11:17:29 UTC+1, Richard Bywater wrote: > > Yes it is workable/feasible as I've just finished setting up a few docker > containers to run as Jenkins slaves. > > In the end I couldn't use the Docker Jenkins plugin as there's an issue > with it not creating a new instance of a container if there is already a > job running with the same label (which kind of defeats the point of using > the Docker plugin IMHO) > > So I created the Docker containers (based off of what has been done with > https://registry.hub.docker.com/u/evarga/jenkins-slave/ ) and then > started them and created nodes on Jenkins to point at them using the > various SSH ports created as part of starting the Docker container. > > Hope that helps you understand that its possible. > > Richard. > > On Thu, 28 May 2015 at 22:13 Piotr Boniek <[email protected] <javascript:>> > wrote: > >> Hi, >> >> I am trying to utilize our new server HP G9. There are many cores, disks >> spaces .... So far we had one master jenkins server and 15 workers on >> different servers. >> It is working fine. Now we want to use one server G9 as multiple worker >> in other words we want to setup 20 or more workers on one physical server. >> To make it more flexible we wanted to use docker to have possibilities to >> setup different workers type eg one on Ubuntu another on RHEL6 or RHEL7... >> >> I've created different users (jenkins, jenkisn1....) separate directories >> etc ... and many many things. >> >> I've tried to accomplished it with Docker Jenkins Plugin or just by >> running 'docker run .... ' from Execute Shell command. I faced so many >> issues that describing >> them maybe is too much for now but maybe later I can post them if needed. >> >> What I want to know is if my idea is workable/feasible? >> >> Regards >> Piotr >> >> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/312c7f68-e97d-41a2-bbeb-cd36a7139cb2%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/312c7f68-e97d-41a2-bbeb-cd36a7139cb2%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b73d1802-0382-451b-9a6b-94ea4ad9380a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
