Comment 1 for bug 1253429
Revision history for this message
| Antoine "hashar" Musso (hashar) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Following a conversation with Khai Do:
There is an option on slave nodes to prevent them from running jobs that are not explicitly tied for them. That shows up in the node configuration as Usage: …
A real life use case is having a slave with node.js package manager npm. That slave does not have any other utilities and thus is dedicated to run javascript tests. The slave receives label hasNpm and is restricted to only run jobs explicitly tied to it.
In Jenkins config.xml the Usage: menu generate a <mode /> entry that takes either NORMAL or EXCLUSIVE has a value.
The Jenkins model Node has a canTake( Task ) method which is used by the queue to find out whether a node is able to launch it. Might want to reuse that logic?