Thanks for the advice - I'll take it back to the team and see what they think. In the meantime, is there anyone out there currently running multiple executors who is using a different approach that is working for them? I'd like to have as many options as possible.
Thanks! On Monday, December 16, 2013 7:00:11 PM UTC-5, Marc MacIntyre wrote: > > One option, assuming you don't have port conflicts, is to define multiple > slaves on the same physical host, with separate filesystem roots, so they > all use different values for $WORKSPACE. > > > On Mon, Dec 16, 2013 at 12:05 PM, Gregory Roberts > <[email protected]<javascript:> > > wrote: > >> Our team has always run 1 executor per slave as hardware hasn't been our >> biggest hurdle, but we'd like to experiment with adding executors to >> hopefully keep our queue moving and not force developers to wait around for >> particular agent types. My concern is how we keep builds that could >> potentially be sharing runtime items, and/or could attempt to remove items >> that another build is using on that agent, from conflicting with one >> another. Can anyone who is currently using 2 or more executors offer some >> insight into what we need to consider, and how we can get around conflicts? >> It seems that multiple executor use is widespread, but the information >> about it is not. >> >> Thank you! >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > 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/groups/opt_out.
