On Fri, Feb 15, 2013 at 07:54:25PM +0530, Olivier Lamy wrote:
> 2013/2/15 Prasanna Santhanam :
> > 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 project
2013/2/15 Prasanna Santhanam :
> 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.
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
Hi,
The repo is not cloned fully for each build (except when a new node is used).
There is a pull not a fully clone (except if you use option "Wipe out
workspace before build").
So that must not be so slow ?
My issue with this plugin is that it will generate some overload on
master (this cloning fe
Greetings all,
I work on the Apache CloudStack (incubating) project and would like to
request for adding a plugin to builds@ jenkins. The Clone Workspace
plugin would be useful to our project that has a ~500MB git repo.
Instead of having the repo downloaded each time a job is created it would
be g
