It seems pretty inflexible. Why not just separate polling from checkout? One step to poll repositories, and one step to checkout.
On Friday, January 17, 2014 1:18:06 PM UTC-8, LesMikesell wrote: > > It is pretty much the point of the slave agent and the way jenkins > works to do all of the remote work for you. I wasn't sure if you did > not understand that or if you had some special requirement to run your > own remote ant script. If you want some things to be copied back to > the master, add a post-build action to 'archive the artifacts' and > specify the files you want. > > -- > Les Mikesell > [email protected] <javascript:> > > > On Fri, Jan 17, 2014 at 9:35 AM, kgiloo <[email protected] <javascript:>> > wrote: > > Thank you so much for your explanation! > > It seems now easy to define a new slave, trigger svn update on it with > SCM > > poll, and execute the Ant script from that location. > > Don't need even my Ant remote task anymore with jenkins slave agent... > > > > > > On Thursday, January 16, 2014 10:05:12 PM UTC+1, LesMikesell wrote: > >> > >> My builds are all done on slaves and even though the master controls > >> the SCM polling, it does not check out any source locally on the > >> master. However, with usual setup, the slave checks out a copy of > >> the target the job is configure to poll before executing anything in > >> the job. So I don't understand how you avoid that - or why you want > >> to avoid it and make your own ant script do the slave checkout. > >> And I think whatever it is you are doing is making the master do the > >> checkout instead of the slave. > >> > >> > >> On Thu, Jan 16, 2014 at 8:18 AM, kgiloo <[email protected]> wrote: > >> > Sorry, i did not get your point... What do you mean exactly? > >> > > >> > On Thursday, January 16, 2014 5:31:05 AM UTC+1, LesMikesell wrote: > >> >> > >> >> On Wed, Jan 15, 2014 at 2:42 AM, kgiloo <[email protected]> > wrote: > >> >> > > >> >> > probably my description lacked precision: > >> >> > I should have titled "A way to get rid of useless checkout of > >> >> > repository > >> >> > into my local workspace". > >> >> > > >> >> > I do not use any special slave configuration to trigger my builds > on > >> >> > slaves, > >> >> > it is all driven by Ant. > >> >> > In other words, checkout of repository is also performed by Ant on > >> >> > slave. > >> >> > > >> >> > I need the "poll SCM" to kick off the build process, for nothing > >> >> > else, > >> >> > i.e > >> >> > checkout of repository in workspace has no sense on my master. > >> >> > >> >> Why do it that way? Why not include the ant script in the checkout > >> >> and let jenkins do it in the right place for you? > >> >> > >> >> -- > >> >> Les Mikesell > >> >> [email protected] > > > > -- > > 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] <javascript:>. > > 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/d/optout.
