I'm not sure it matters; ultimately, the job is going to run on some kind of slave, right? That slave's node property can then query the "server that manages these hardware resources" in the canTake() method, and return the appropriate response. If all available slaves refuse the job, then it gets queued.
On Tue, Oct 14, 2014 at 3:57 PM, Ian Wakely <[email protected]> wrote: > I don't think the hardware that I'm trying to manage can be a node, as > they are being re-flashed with new firmware and having different operating > systems installed onto them periodically to test different functionality. > Having anything running on them would probably corrupt the tests that are > trying to be performed. > > On Tuesday, October 14, 2014 5:13:04 PM UTC-5, Marc MacIntyre wrote: >> >> I implemented this by defining a node property on the computer, then had >> the canTake method check the availability and respond accordingly: >> >> http://javadoc.jenkins-ci.org/hudson/slaves/NodeProperty. >> html#canTake(hudson.model.Queue.BuildableItem) >> >> On Tue, Oct 14, 2014 at 3:08 PM, Ian Wakely <[email protected]> wrote: >> >>> I'm trying to write a plugin that will claim this networked hardware >>> resource and queue the job instead of the resource is not available. I'm >>> able to get a job to queue with other jobs by having a class implement >>> ResourceActivity. However, I've been having problems on trying to determine >>> is the resource that is needed by a job is physically available on the >>> network. There is a server that managers these hardware resources and I can >>> get the plugin to communicate with that, its just the actual queuing based >>> on it that I'm having problems with. Some suggestions on the correct way of >>> how to go about this would be much appreciated. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Marc MacIntyre >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Marc MacIntyre -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
