[JIRA] (JENKINS-39780) Git clone timesout

lgawel@cayan.com (JIRA)

unread,

Nov 16, 2016, 11:13:04 AM11/16/16

to jenkinsc...@googlegroups.com

Lukasz Gawel created an issue

Jenkins /

JENKINS-39780

Git clone timesout

Issue Type:	Bug
Assignee:	Mark Waite
Components:	git-client-plugin
Created:	2016/Nov/16 4:12 PM
Priority:	Major
Reporter:	Lukasz Gawel

After updating to newest version of Git client 2.1.0 Git Clone times out.

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

mark.earl.waite@gmail.com (JIRA)

unread,

Nov 16, 2016, 8:36:02 PM11/16/16

to jenkinsc...@googlegroups.com

Mark Waite commented on

JENKINS-39780

Re: Git clone timesout

Please provide detailed instructions to duplicate the problem, and provide the configuration changes you've tried in an attempt to resolve the issue.

For example, have you

tried with JGit rather than command line git?
tried with JGit apache rather than command line git?
verified that the credentials you're using work outside Jenkins?
tried on a different platform or operating system or command line git version?
tried with a different git hosting provider?
confirmed that there are authentication cases which still work in your environment?
requested help from the Jenkins users mailing list?

Add Comment

lgawel@cayan.com (JIRA)

unread,

Nov 17, 2016, 8:06:07 AM11/17/16

to jenkinsc...@googlegroups.com

Lukasz Gawel commented on

JENKINS-39780

Re: Git clone timesout

Hi Mark,

I haven't tried using JGit, how do I do that with Jenkinsfile? I'm executing "checkout scm" command. This issue went away as soon as I downgraded back to git-client 2.0.0. Also my slaves are windows VMs with 'git version 2.10.2.windows.1' on them.

Add Comment

mark.earl.waite@gmail.com (JIRA)

unread,

Nov 17, 2016, 9:27:01 AM11/17/16

to jenkinsc...@googlegroups.com

Mark Waite commented on

JENKINS-39780

Re: Git clone timesout

The "checkout scm" pipeline syntax helper will show you the options to configure the detailed checkout definition, and that detailed definition should be able to use jgit if you enable JGit as a globally available git implementation from the "Global Tools Configuration" link in the "Manage Jenkins" page.

What is the version number of the previous version of the git client plugin that you were using?

When I asked for a detailed description of the steps to duplicate the problem, that was intended to help you explore and discover what might be different between the previously working environment and the failing environment. You might also review JENKINS-38138, JENKINS-38179, and JENKINS-38194, in case one of them matches your configuration. You didn't provide configuration information, so I can't decide if your configuration is similar to theirs or not.