Hi, Updated to Jenkins ver. 1.452, server on Windows 2003, JNLP slave on Windows 7. Slave has been updated to same version as server. Upgraded from 1.445
I have jobs assigned to a specific slave that even while the slave is available with no running jobs, they will just sit there "waiting for next available executor on NAME". This happens when I kick off the build manually, not sure about automatic yet. Nothing I can do manually will ever cause the job to start executing on the slave (e.g. stopping/starting the slave service, marking the node as temp unavailable, etc). However as soon as any other job is assigned to any other slave, the job for the problematic slave will also be immediately assigned to it. Is this a known bug? If not, what is the best way to diagnose the cause? Regards, Brodie
