On Fri, Feb 15, 2013 at 07:54:25PM +0530, Olivier Lamy wrote: > 2013/2/15 Prasanna Santhanam <[email protected]>: > > Thanks - I understand it's not clone per build. Also I set the > > topmost upstream job on a node to fetch changes from repo using git > > and clone the same workspace for all other downstream projects on the > > same node. This (I assume) prevents copies across master. But this is > > convention which cannot be imposed for builds@. > > > > Am I right in assuming that copy of zip archive to master happens > > regardless of all the clone related jobs being on the same node? This > > is something I wasn't aware of. That seems bad. > Except if you use only one single node for all your builds. But not > sure it's a good idea for having fast builds. > Do you really want that. > BTW we talk here about a zip/tar archive of the workspace but it can > generate a bit of network transfer.
I'm okay with not enabling the plugin atm if this archive copy through master is what it can potentially do. I'll do a few tests on my setup. I do have a few nodes on my setup but the jobs tied to a given node only have one (frequent) job that fetches from the repo and rest clone the workspace from that job tied to version control. -- Prasanna.,
