As we need a lot of manually installed tools, we decided to have strictly separated slaves and provide rather lots of labels to get each project built on the right slave. This works really good so far. Now we thought we could spare at least the label for the JDK, as Jenkins in a sense has all needed information to pick the right slave for a needed JDK: * All used JDKs are provided in the Jenkins core configuration, and all of them are marked as "do not install automatically". * Each project has the "Used JDK" set to a particular JDK. * Each node has a list of all manually installed JDKs. Hence, if Jenkins needs to pick a Slave from the list of possible nodes, it can "see" which of those have the needed JDK for a particular project installed. Unfortunately it does not. In fact, it picks just ANY, even one that has not the needed JDK installed.
Certainly this can be easily worked around by using another label for the JDK, but we think this is redenundant information. If Jenkins can auto-install a missing JDK, why can't it in turn not simply use a different slave if the JDK is missing for those not wanting to use auto-install? -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
