I was considering using the matix job, but it has a major flaw, it will be queued with the regular builds...we have one executor per slave and some of the jobs run for a long time ~30 minutes, so on part of the slaves it will wait for a long time in the queue. I'm ok with t processing one by one from the script console, i'm just failing to do so :S if I could only add an executor in the beginning of the build and remove it afterwards...
any ideas about the script ? On Sunday, December 15, 2013 6:18:57 PM UTC+2, LesMikesell wrote: > > On Sun, Dec 15, 2013 at 6:05 AM, Omer Weissman > <[email protected]<javascript:>> > wrote: > > > > Thanks for the idea, I didn't try dsh, and I was not familiar with it. > > But I still want to accomplish this through Jenkins Console, as dsh > requires me to be in the same LAN or use VPN, and I want to be able to do > it through the interface. > > > > any ideas ? > > I think the script console can only connect to one node at a time. > You could put you command in a matrix (multi-configuration) job and > select all the nodes, though. > > -- > Les Mikesell > [email protected] <javascript:> > -- 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.
