The system with which I am working uses nodes that are brought online as needed, and taken offline if they are not immediately used again (within two minutes) when a job is complete.
Using the “restrict where this job can be run” or the Parameterized Build (using a label), the master does not bring an additional node online for a newly triggered job if there is already a node online which matches that label. This is not the desired behavior. Right now, this blocks the build queue by making the new job wait until the job already running on the online node is finished (multiple hours in some cases). I need the master to bring a node (with matching label) online for a new job unless there is already a FREE node online matching that label. Jenkins knows these jobs are waiting too, because the logs show "Launching machine XXXXX because it has been in demand for 1 hr 28 min". -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/89cf70ae-f350-479e-b2f3-dafb20322061%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
