help troubleshoot the issue further,
please let me know.
Thanks,
Terry
From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite
Sent: Tuesday, February 11, 2014 6:21 PM
To: jenkinsci-users@googlegroups.com
That's correct, the units are minutes.
On Tue, Feb 11, 2014 at 9:03 PM, Curtis Kline wrote:
> Thanks Mark. I'll try running my Windows slave from the command line. So
> the timeout value is in minutes?
>
> Curtis
>
>
>
> On Tue, Feb 11, 2014 at 5:54 PM, Mark Waite wrote:
>
>> Sorry, I gave bad
Thanks Mark. I'll try running my Windows slave from the command line. So
the timeout value is in minutes?
Curtis
On Tue, Feb 11, 2014 at 5:54 PM, Mark Waite wrote:
> Sorry, I gave bad information. The timeOut property I listed is incorrect.
>
> It should be -Dorg.jenkinsci.plugins.gitclient.G
Sorry, I gave bad information. The timeOut property I listed is incorrect.
It should be -Dorg.jenkinsci.plugins.gitclient.Git.timeOut=30
On Tue, Feb 11, 2014 at 6:34 PM, Mark Waite wrote:
> If you have control of the git repository, and if you don't mind allowing
> the source code to be readab
If you have control of the git repository, and if you don't mind allowing
the source code to be readable by anyone inside your network, you could
enable a git protocol server in addition to your ssh protocol server. The
download speed through git protocol is very near wire speed, so should be
fast
Thanks Mark. I think you're right.
My current problem involves projects that really can't wait for my testing
of the next release of the git plugin (although I am definitely interested
in doing that). Any short-term suggestions on how to get this to work with
my current setup? I thought about swit
Curtis, I think your problem is a different problem than the original
description from Terry.
I believe Terry is attempting to clone a repository which should clone in
significantly less than 10 minutes, while you already know that your clone
will take more than 10 minutes (due to the size of the
My technique is the opposite of Slide's. I always use the git executable
in the bin directory. There were issues reported when the git executable
in the cmd directory was used instead of using the executable in the bin
directory.
You might consider a "test drive" of the JGit implementation in yo
I ran into the same problem today for the first time. I am using Git plugin
1.5.0 (still scared to jump to 2.0) and Git Client Plugin 1.6.1. I don't
use plink, but rather the ssh included with msysgit 1.8.5. My Windows
slaves are connected using JNLP.
I desperately need some way to control that ti
What is the path to Git? I use the one in ProgramFiles\Git\cmd instead of
ProgramFiles\Git\bin.
On Tue, Feb 11, 2014 at 4:49 PM, Dunnigan, Terrence J <
terrence.j.dunni...@boeing.com> wrote:
> Hi all,
>
>
>
> I've run into an issue where the latest git plugin / git client plugins
> time out. It
Hi all,
I've run into an issue where the latest git plugin / git client plugins time
out. It pulls down the files in .git\objects\pack and elsewhere, but nothing
beyond the .git folder.
Here's my setup:
Jenkins server:
Jenkins LTS 1.532.1 running on a Windows 7 PC
Jenkins GIT client plugin 1.6
11 matches
Mail list logo
