[Jenkins] poor handling of offline slaves

[Kristian Waagan]

Hi,

Currently there are several jobs that have been hanging on a Linux 
executor for several days because windows1 is offline. In addition, 
there are a bunch of jobs that have been in the queue for days.
It appears that Jenkins lets the "multi OS" jobs wait for a very long 
time before giving up on waiting for a slave. A few questions:
 a) Is it possible to have Jenkins fail a job already occupying an 
executor slot if it has to wait for too long?
 b) There's only one windows slave. Are there any plans to add another 
Windows slave (preferably on a different box than windows1)?

If many projects are configured to run on multiple operating systems, of 
which two have only one slave (Windows and Solaris), these projects may 
cause jobs to pile up on Linux. Maybe there are other mechanisms in 
place to deal with this, I don't know.

There are currently two other jobs [1]  that have been hanging for two 
days or more, but there seems to be enough Linux executors to serve 
other jobs reasonably fast. For that reason I have left them alone for 
the time being.


Thanks,
--
Kristian

[1] https://builds.apache.org/job/Ant-Build-Matrix/ and 
https://builds.apache.org/job/Empire-db%20multios/