we found the latest jenkins and docker plugin work better together. Older versions would not always fire up a slave when they where supposed to - or fired up the wrong slave type!
if you can upgrade to the next soon to be stable LTS and give it a go you may find it works better. On Tuesday, 14 October 2014 21:48:15 UTC+1, Richard Bywater wrote: > > How long have you waited for it to start a new node? I've found it can > take quite a while (minutes) which apparently is caused by > https://issues.jenkins-ci.org/browse/JENKINS-24752. Not sure if thats the > case in your instance though. > > If you have a label which only contains docker providers does it work? > > Richard. > > On Wed, Oct 15, 2014 at 1:10 AM, Daniel Laird <[email protected] > <javascript:>> wrote: > >> All, >> >> I am using the docker-plugin and provisioning containers as I require >> them. >> I am using the latest LTS Jenkins release. >> >> I have some non cloud based slaves with a label of ubuntu_12.04 and I >> also use this label for the docker containers. >> If I take all the non-cloud slaves offline (which is my goal). >> Then Jenkins fails to launch a slave on the cloud. >> >> I get lots of debug suggesting that there is a need for a slave: >> >> Current time: Oct 14, 2014 1:07:52 PM BST. Next execution (DIFF) in 24,780 >> seconds which is Oct 14, 2014 8:00:52 PM BST >> >> Oct 14, 2014 1:07:55 PM FINE hudson.slaves.NodeProvisioner >> >> Excess workload 1.0 detected. (planned >> capacity=0.0,Qlen=0.99993694,idle=0.0&0,total=0m,=0.5) >> >> Oct 14, 2014 1:08:05 PM FINE hudson.slaves.NodeProvisioner >> >> Excess workload 1.0 detected. (planned >> capacity=0.0,Qlen=0.99994326,idle=0.0&0,total=0m,=0.5) >> >> Oct 14, 2014 1:08:15 PM FINE hudson.slaves.NodeProvisioner >> >> Excess workload 1.0 detected. (planned >> capacity=0.0,Qlen=0.9999489,idle=0.0&0,total=0m,=0.5) >> >> Oct 14, 2014 1:08:25 PM FINE hudson.slaves.NodeProvisioner >> >> Excess workload 1.0 detected. (planned >> capacity=0.0,Qlen=0.99995404,idle=0.0&0,total=0m,=0.5) >> >> Oct 14, 2014 1:08:35 PM FINE hudson.slaves.NodeProvisioner >> >> Excess workload 1.0 detected. (planned >> capacity=0.0,Qlen=0.99995863,idle=0.0&0,total=0m,=0.5) >> >> >> I have enabled the following debug: >> >> com.nirima >> >> hudson.plugins >> >> hudson.slaves >> >> >> And I am getting no more useful debug. >> >> What do I have to do to get a Slave created? Is it a problem with the >> algorithm or the plugin? >> >> >> Hope you can help >> >> Dan >> >> -- >> 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] <javascript:>. >> 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.
