Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48933

Unstoppable Multibranch Pipeline Scan

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Jenkins ver. 2.89.2
      Multibranch Pipeline plugin ver. 2.16
    • Similar Issues:

      Description

      In rare occasions, our Jenkins master (2.89.2) gets into a state in which multiple pipeline scans are completely stuck.

      Clicking on the icon does not abort the scan but leads to the error message "Are you sure you want to abort null?"

      The Scan Multibranch Pipeline Log shows the following plus a little spinner icon...

      Started by timer
      [Sun Jan 14 02:59:42 CET 2018] Starting branch indexing...
      

      It seems that git cannot be accessed and for some reason the scan never gives up. In fact, our git went shortly offline a day ago, which might have caused this, but still I would assume that the scan has some kind of time out. New scans of other pipelines work perfectly fine while the four listed above cannot be cancelled. Only a Jenkins restart has helped last time this happened.

      Stack trace of the 4 blocked threads, taken from Melody:

      Executor #-1 for master : executing BranchIndexing[My_Pull_Request_Pipeline]
      java.net.SocketInputStream.socketRead0(Native Method)
      java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
      java.net.SocketInputStream.read(SocketInputStream.java:170)
      java.net.SocketInputStream.read(SocketInputStream.java:141)
      sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
      sun.security.ssl.InputRecord.read(InputRecord.java:503)
      sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
      sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930)
      sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
      java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
      java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
      java.io.BufferedInputStream.read(BufferedInputStream.java:345)
      sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704)
      sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
      sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569)
      sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
      java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
      sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
      org.eclipse.jgit.transport.http.JDKHttpConnection.getResponseCode(JDKHttpConnection.java:98)
      org.eclipse.jgit.util.HttpSupport.response(HttpSupport.java:190)
      org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:465)
      org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:290)
      org.jenkinsci.plugins.gitclient.JGitAPIImpl.getRemoteSymbolicReferences(JGitAPIImpl.java:831)
      jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:937)
      jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746)
      jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:588)
      com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276)
      com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)
      jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1022)
      hudson.model.ResourceController.execute(ResourceController.java:97)
      hudson.model.Executor.run(Executor.java:421)
      

        Attachments

          Activity

          Hide
          dthomash Dylan H added a comment -

          I am seeing the same issue with Perforce Stream multibranch scanning. Restarting Jenkins seems to resolve it for us, but it is certainly a less than elegant workaround.

          Show
          dthomash Dylan H added a comment - I am seeing the same issue with Perforce Stream multibranch scanning. Restarting Jenkins seems to resolve it for us, but it is certainly a less than elegant workaround.
          Hide
          jgrant216 Jeff G added a comment -

          Same issue.  Does anyone have a way to abort these?  I tried using Scriptler as though it were a build but could not find the right combination.

          Show
          jgrant216 Jeff G added a comment - Same issue.  Does anyone have a way to abort these?  I tried using Scriptler as though it were a build but could not find the right combination.
          Hide
          bitwiseman Liam Newman added a comment -

          Is this specific to git based multibranch projects? Mark Waite does this looks familiar to you?

          Show
          bitwiseman Liam Newman added a comment - Is this specific to git based multibranch projects? Mark Waite does this looks familiar to you?
          Hide
          markewaite Mark Waite added a comment -

          Liam Newman the stack trace in the bug report is specific to git based multibranch projects. It is using the JGit implementation to retrieve the remote symbolic references.

          This report is based on git client plugin 2.x and git plugin 3.x (based on when it was submitted). One or more of the submitters might want to try git client plugin 3.0.0 and git plugin 4.0.0. They switched to JGit 5.5.0 instead of the JGit 4.x version that was included in git client plugin 2.x and git plugin 3.x.

          They might also want to try with git client plugin 3.1.0-beta and git plugin 4.1.0-beta so that they could test JGit 5.6.0 instead of JGit 4.x.

          Show
          markewaite Mark Waite added a comment - Liam Newman the stack trace in the bug report is specific to git based multibranch projects. It is using the JGit implementation to retrieve the remote symbolic references. This report is based on git client plugin 2.x and git plugin 3.x (based on when it was submitted). One or more of the submitters might want to try git client plugin 3.0.0 and git plugin 4.0.0. They switched to JGit 5.5.0 instead of the JGit 4.x version that was included in git client plugin 2.x and git plugin 3.x. They might also want to try with git client plugin 3.1.0-beta and git plugin 4.1.0-beta so that they could test JGit 5.6.0 instead of JGit 4.x.
          Hide
          vikas_rubrik Vikas Goel added a comment -

          Hi,

          I am still noticing this issue. When I try to abort the "Scan Repository Now", it doesn't stop and continue scanning the repository.

          Show
          vikas_rubrik Vikas Goel added a comment - Hi, I am still noticing this issue. When I try to abort the " Scan Repository Now ", it doesn't stop and continue scanning the repository.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            dokaspar Dominik Kaspar
            Votes:
            17 Vote for this issue
            Watchers:
            28 Start watching this issue

              Dates

              Created:
              Updated: