Resource mange external nodes in Jenkins for tests -
my problem have code need rebooted node. have many long running jenkins test jobs needs executed on rebooted nodes.
my existing solution define multiple "proxy" machines in jenkins same label (testlable) , 1 executor per machine. bind test jobs label (testlable). in test execution script detect jenkins machine (jenkins env. node_name) , use know physical physical machine tests should use.
do know of better solution?
the above works need define high number of “nodes/machines” may not needed. plugin able grant token jenkins job. way job not executed before jenkins executor , token free. token should string test jobs use know external node use.
we have written our own scheduler allocates stuff before starting jenkins nodes. there may better solution - works mostly. i've yet come across off-the-shelf scheduler can deal complicated allocation of different hardware resources. have n box types, allocated n build types.
some build types have not compatible without destroying persistent data - may required takes long time gather. jobs require combinations of these hardware types. store details in db, , use business logic determine how allocated. we've found particular job types need additional business logic or data fields account specific requirements.
so may best way write own scheduler, in own language of choice, takes account particular needs.
Comments
Post a Comment