Does Jenkins have any concept of local system load on it's slaves/permanent agents for scheduling? I know by default it favors the last executor for a job. I've looked at the Least-Load plugin too, but it seems like it only knows about the number of defined executors available regardless of any other local jobs that may be running. Is it intended that permanent agents are used exclusively by Jenkins?
I have seen some people mention using users' workstations as extra executors, but other than limiting number of jobs it doesn't seem like a good idea. In my case (I'm in digital hardware design, not software), we have dedicated servers to run large jobs, but as I'm exploring Jenkins I can't segregate a machine exclusively for Jenkins and don't foresee others adopting this strategy for a long while. We actually have LSF for scheduling, but it's not enforced so people often login to these machines directly. That's a whole other topic for discussion, but at least it's scheduling algorithm takes into account system load and resources not just slots. I've tried the LSF cloud plugin, but I don't think it aligns with our setup as I don't have to login to a specific machine with a different user to submit jobs or pre-transfer files. We have a shared network filesystem so everything can be available to all hosts. I can also add LSF hosts as permanent agents, but if Jenkins can't otherwise know a machine is fully booked up outside of it's control there's no way they should co-exist (but this is similar to sharing users' workstations which is why I mentioned above). My last resort is to just call LSF 'bsub' (maybe write a groovy script wrapper function) as part of each stage's shell command that just adds complexity to the script though. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/10101dd6-aaad-48a5-abaa-a04991de6a4e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
