On Wednesday, August 20, 2014 4:22:52 PM UTC-6, Mark Waite wrote:
>
> You could use the add "Additional Behaviour" for "Advanced clone option"
> to a define a reference repository. A reference repository will provide
> the same data transfer reduction, without the complexity of defining two
>
I believe I have figured out what the problem is. Still trying to find a
reasonable workaround.
I had two git repositories defined - one of which was a local cache of the
full git repo that got cloned when the slave starts up (referenced as a
file:// repo) and then the actual github repo. It lo
(if 2.2.4 behaves more the way you want).
>
> Thanks,
> Mark Waite
>
>
> On Tue, Aug 19, 2014 at 4:03 PM, Nicholas Paufler > wrote:
>
>> We're using Jenkins 1.575 with the GIT client (1.10.1), GIT (2.2.5), and
>> GitHub (1.24) plugins (amongst oth
We're using Jenkins 1.575 with the GIT client (1.10.1), GIT (2.2.5), and
GitHub (1.24) plugins (amongst others) but the issue seems to be related to
those in some fashion.
Specifically, we're using the Jenkins Build Per Branch script
(http://entagen.github.io/jenkins-build-per-branch/) to creat
