> There is no way to force the plugin to use clone instead of fetch. Even
> if there were, it would likely have the same problem, since clone is often
> described as "init + fetch".
>
>
That was meant as a way to try to overcome what seems to be a bug in the
plugin, not sure it would have cha
There is no way to force the plugin to use clone instead of fetch. Even if
there were, it would likely have the same problem, since clone is often
described as "init + fetch".
You could reduce the amount of data transferred by using a shallow clone.
That's one of the checkboxes in the "Additional
Hi,
I am trying to get a repository cloned inside a Jenkins job. The cloning
operation works, but the downloaded data is way too much, and we are having
issues since the site is on low bandwidth and the programmers want the
workspace to be cleaned out at each run.
The git repository needs authe
