I have 17 slaves and soon will have more, so adding another maintenance agent per machine is a huge overhead...
I'm aware of the execute().text as I understand, from the manage console it will only run on the master. please see my original post for the loop trying to accomplish this. many thanks On Monday, December 16, 2013 6:10:26 PM UTC+2, LesMikesell wrote: > > On Mon, Dec 16, 2013 at 9:24 AM, Omer Weissman > <weis...@gmail.com<javascript:>> > wrote: > > 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... > > You can run more than one slave agent on a machine - which lets you > give them different node names and labels to control what they > execute. > > > any ideas about the script ? > > The script console runs groovy, which gives an execute() method to > quoted strings. Have you tried something like: > println "your_command".execute().text > in the script console? If the target is windows you may have to keep > in mind that some of the things you think are commands are build into > the cmd program. > > -- > Les Mikesell > lesmi...@gmail.com <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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
