[travis-ci] dtolabs/rundeck#235 (development - 90a25f3 : Greg Schueler): The build passed.
[travis-ci] Change view : https://github.com/dtolabs/rundeck/compare/c79f45d13160…90a25f33060a
[travis-ci] Build details : http://travis-ci.org/dtolabs/rundeck/builds/6933029
[travis-ci] dtolabs/rundeck#236 (development - cdfa1c8 : Greg Schueler): The build passed.
[travis-ci] Change view : https://github.com/dtolabs/rundeck/compare/90a25f33060a…cdfa1c8963b8
[travis-ci] Build details : http://travis-ci.org/dtolabs/rundeck/builds/6937087
is it possible to have a workflow where step 1 applies to node set N, and step 2 applies to node set M?
you can create 2 jobs, with different node sets, and wrap them in a job that calls each in turn
if thats what you meant
yeah I think I don’t know about job nesting
what I want is
issue a command
then watch and wait for something to happen
then when I see that thing happen run another command
repeat that over sets of nodes in turn.
I have an HPC cluster with 400 nodes. I want to close them to new jobs, wait for jobs to finish, then run a command, then re-open them, in batches of say 10 or 20 nodes.
im not sure I completely understand, but you want to execute a cmd (close), wait for something, execute a cmd(open) on 10 nodes, then move to the next batch of 10?
until all 400 nodes have had that happen?
seems like you have to define a target set of nodes with a job
rather than defining a job, then applying it to a set of nodes in a workflow.