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]. For more options, visit https://groups.google.com/groups/opt_out.
