Mark Waite commented on Bug JENKINS-20387

You will need to remove the Git plugin 2.0 and download from https://updates.jenkins-ci.org/download/plugins/ the 1.5.0 or earlier version.

I've searched the code with my limited knowledge of the plugin implementation and could not find an obvious location where the timeout was controlled. We'll probably need help from the plugin maintainer or from Kohsuke.

I handled my issue with the timeout by:

  1. Disable the job which can't clone because it takes longer than the timeout
  2. Login as the Jenkins user on the machine which hosts that job
  3. Use a "git clone" command in the Jenkins workspace directory for that job to clone the repository
  4. Enable the job, and let it run

I admit that is an ugly work around for the root problem, but it worked for me.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to