Since version 2.59 there is a problem when checking out Git repositories on any of our projects. Jenkins seems to hang:

      Fetching changes from the remote Git repository

      Cleaning workspace

      ...and that's it.

      When looking into the Jenkins logs I see the following exception:

      May 08, 2017 11:34:47 AM hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException SEVERE: A thread (Thread-17/172) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.NullPointerException at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:447) at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:790) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:502) at java.lang.Thread.run(Thread.java:745)

      Updated from 2.53 to 2.59, updated OpenJDK from 1.7 to 1.8. Jenkins running on Ubuntu 15.

          [JENKINS-44120] Git checkout hangs after update on 2.59

          Christoph M created issue -
          Christoph M made changes -
          Description Original: Since version 2.59 there is a problem when checking out Git repositories on any of our projects. Jenkins seems to hang:

          {{Fetching changes from the remote Git repository}}

          {{Cleaning workspace}}

          ...and that's it.

          When looking into the Jenkins logs I see the following exception:

          {color:#707070}{{May 08, 2017 11:34:47 AM hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException SEVERE: A thread (Thread-17/172) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.NullPointerException at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:447) at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:790) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:502) at java.lang.Thread.run(Thread.java:745)}}{color}
          New: Since version 2.59 there is a problem when checking out Git repositories on any of our projects. Jenkins seems to hang:

          {{Fetching changes from the remote Git repository}}

          {{Cleaning workspace}}

          ...and that's it.

          When looking into the Jenkins logs I see the following exception:

          {color:#707070}{{May 08, 2017 11:34:47 AM hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException SEVERE: A thread (Thread-17/172) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.NullPointerException at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:447) at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:790) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:502) at java.lang.Thread.run(Thread.java:745)}}{color}

          {color:#707070}---{color}

          {color:#707070}Updated from 2.53 to 2.59, updated OpenJDK from 1.7 to 1.8. Jenkins running on Ubuntu 15.{color}
          Mark Waite made changes -
          Assignee Original: Mark Waite [ markewaite ]
          Mark Waite made changes -
          Component/s New: trilead-api-plugin [ 22324 ]
          Component/s Original: git-plugin [ 15543 ]

          Mark Waite added a comment -

          Can you confirm that you're using JGit as your git implementation for that job, rather than command line git?

          Can you provide enough steps so that someone else can duplicate the problem?

          I've reassigned the report to the trilead plugin since that has been changed recently to update to a newer version.

          Mark Waite added a comment - Can you confirm that you're using JGit as your git implementation for that job, rather than command line git? Can you provide enough steps so that someone else can duplicate the problem? I've reassigned the report to the trilead plugin since that has been changed recently to update to a newer version.

          Christoph M added a comment - - edited

          Yes, JGit is the only configured (and used) git tool.

          The checkout process is done in a pipeline by this code:

          checkout([$class: 'GitSCM', branches: [[name: BRANCH_NAME]], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CleanBeforeCheckout']], submoduleCfg: [], userRemoteConfigs: [[credentialsId: '...', url: 'git@github.com:.../....git']]])

          but also the multibranch / branch tracking project isn't able to access (prune) the repository.

          Christoph M added a comment - - edited Yes, JGit is the only configured (and used) git tool. The checkout process is done in a pipeline by this code: checkout([$class: 'GitSCM', branches: [ [name: BRANCH_NAME] ], doGenerateSubmoduleConfigurations: false, extensions: [ [$class: 'CleanBeforeCheckout'] ], submoduleCfg: [], userRemoteConfigs: [ [credentialsId: '...', url: 'git@github.com:.../....git'] ]]) but also the multibranch / branch tracking project isn't able to access (prune) the repository.

          Hi, I have the same issue. JGit, Oracle JDK 8u131, Jenkins 2.61, Windows server slave.

          Please look into this - this issue is preventing all the jobs from running.

          Vlastimil Dolejš added a comment - Hi, I have the same issue. JGit, Oracle JDK 8u131, Jenkins 2.61, Windows server slave. Please look into this - this issue is preventing all the jobs from running.

          Christoph M added a comment -

          I also just tested it with v2.61. The problem still exists.

          Christoph M added a comment - I also just tested it with v2.61. The problem still exists.
          Mark Waite made changes -
          Assignee New: Michael Clarke [ mc1arke ]

          Can anyone who is having this issue provide details about the server they're SSHing in to when checking out the Git repository - i.e. Operating System and SSH host software versions and configurations? Primarily running ssh -vv git-host (where git-host is the host you're trying to checkout from) should give an idea about the MACs, Ciphers and Key Exchange algorithms your Git host is offering, but also checking your SSH Server's logs for the Git client's connection attempt wold be useful

          Michael Clarke added a comment - Can anyone who is having this issue provide details about the server they're SSHing in to when checking out the Git repository - i.e. Operating System and SSH host software versions and configurations? Primarily running ssh -vv git-host (where git-host is the host you're trying to checkout from) should give an idea about the MACs, Ciphers and Key Exchange algorithms your Git host is offering, but also checking your SSH Server's logs for the Git client's connection attempt wold be useful

            mc1arke Michael Clarke
            cmuche Christoph M
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: