| That timeout message is typically caused by an authentication failure and command line git waiting for the correct username and/or password to be provided. If you're using TFS as your git server, then this may be a duplicate of JENKINS-38138 or JENKINS-38179. In that case, the work around is to downgrade to git plugin 2.6.0 and git client plugin 1.21.0. If you're using TFS as your git server and the authentication still fails, then that may mean that you need the "jgitapache" git implementation which was just merged to the git client plugin through the work of Olivier Dagenais on JENKINS-37934. In that case, the work around might be to install a pre-release version of what will eventually be git client plugin 2.1.0, then add jgitapache as a valid git implementation and use it in your job definition. If you're not using TFS, but have special characters in the password of the specific user (like caret or ampersand or single quote or double quote), then this may be a duplicate of JENKINS-38194. The work around in that case may be to switch that job from using the command line git implementation to use the JGit implementation. The JGit implementation needs to be enabled globally first from "Manage Jenkins", "Global Tool Configuration", "Git", then there will be a pick list in each job which will allow you to choose whether that job should use command line git or JGit. Another work around in some cases is to switch the job from using https based cloning to using ssh based cloning. That usually changes the URL from an https form to either git@hostname:directory or ssh://user@hostname/directory . As a side note, the Java 8 version you're using was released over 18 months ago. I doubt the Java 8 version that will have any impact on this particular problem, since the timeout came from command line git and that usually indicates an authentication failure. However, 18 months is quite a long time in the world of JDK patches. There have been several releases since then which might matter to you. I'm not aware of any specific problems with that Java 8 version, but I only test with Java 8 builds 101 and 102, not with Java 8 build 31. |
