Sounds like the default scheduler behavior. There's some information on how it works, but it's a bit inconsistent:
"Try to use the last used node": https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds#Distributedbuilds-Schedulingstrategy "Prefer a specific node": http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/even-scheduler.html#d0e271 But let's just say, regular jobs stick to a specific node unless they can't. Build flows don't use regular executors (that can be in use) so they can always run on the same node. There are other scheduler implementations that might change the behavior you see here: https://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/even-scheduler.html Regards, Daniel On 05.07.2013, at 19:16, Tom Deblauwe <[email protected]> wrote: > hello list, > > We are using the buildflow plugin succesfully. We have one job with > parameters and also associated with a label, and italso has the enable > concurrent builds option set. We also have multiple buildslaves with the same > label. We expected that the buildflow jobs are scheduled evenly across the > buildslaves. however, always the same buildnode is used. with regular > freestyle jobs we do not have this issue. Is there a solution? > > thanks, > best regards > Tom > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
