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

Branch Indexing of username/password protected repository fails

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Component/s: git-plugin
    • Labels:
    • Environment:
      git-plugin: 3.6.2
      Jenkins: 2.86
      Windows Server 2012 R2
    • Similar Issues:

      Description

      The branch indexing using the git-client does not work anymore, in case the indexed repository is password protected and requires GIT_ASKPASS to be set.

      The error was introduced in the git-client 3.6.1 and my best guess is that it is related to PR#544.

       At version 3.6.0 the branch indexing looks like this:

      Starting branch indexing...
       > git.exe rev-parse --is-inside-work-tree # timeout=10
      Setting origin to https://****.git
       > git.exe config remote.origin.url https://****.git # timeout=10
      Fetching origin...
      Fetching upstream changes from origin
       > git.exe --version # timeout=10
      using GIT_ASKPASS to set credentials ****
       > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
      using GIT_ASKPASS to set credentials ****
       > git.exe ls-remote --symref https://****.git # timeout=10
       > git.exe rev-parse --is-inside-work-tree # timeout=10
      Setting origin to https://****.git
       > git.exe config remote.origin.url https://****.git # timeout=10
      Fetching & pruning origin...
      Fetching upstream changes from origin
       > git.exe --version # timeout=10
      using GIT_ASKPASS to set credentials ****
       > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --prune
      Listing remote references...
       > git.exe config --get remote.origin.url # timeout=10
      using GIT_ASKPASS to set credentials ****
       > git.exe ls-remote -h https://****.git # timeout=10
      Checking branches...
      

      In Version 3.6.2 this happens:

      Starting branch indexing...
       > git.exe --version # timeout=10
       > git.exe ls-remote --symref https://****.git # timeout=10
      ERROR: [Mi Okt 25 14:48:06 MESZ 2017] Could not update folder level actions from source 1670125f-05be-412b-9264-27212be64b57
      hudson.plugins.git.GitException: Command "git.exe ls-remote --symref https://****.git" returned status code 128:
      stdout: 
      stderr: fatal: Authentication failed for 'https://****.git/'
      
      	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1924)
      	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1643)
      	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1561)
      	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1552)
      	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:2769)
      	at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:804)
      	at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746)
      	at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591)
      	at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276)
      	at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)
      	at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978)
      	at hudson.model.ResourceController.execute(ResourceController.java:97)
      	at hudson.model.Executor.run(Executor.java:421)
      

      Rolling back to the old version, fixes the issue.

        Attachments

          Issue Links

            Activity

            nitram Martin Karing created issue -
            nitram Martin Karing made changes -
            Field Original Value New Value
            Description The branch indexing using the git-client does not work anymore, in case the indexed repository is password protected and requires GIT_ASKPASS to be set.

            The error was introduced in the git-client 3.6.1 and my best guess is that it is related to [PR#544|https://github.com/jenkinsci/git-plugin/pull/544].

             At version 3.6.0 the branch indexing looks like this:

            {code:none}
            Starting branch indexing...
             > git.exe rev-parse --is-inside-work-tree # timeout=10
            Setting origin to http://srv01.tki-chemnitz.de:82/Git/map3d-tools.git
             > git.exe config remote.origin.url http://srv01.tki-chemnitz.de:82/Git/map3d-tools.git # timeout=10
            Fetching origin...
            Fetching upstream changes from origin
             > git.exe --version # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
            using GIT_ASKPASS to set credentials ****
             > git.exe ls-remote --symref https://****.git # timeout=10
             > git.exe rev-parse --is-inside-work-tree # timeout=10
            Setting origin to https://****.git
             > git.exe config remote.origin.url https://****.git # timeout=10
            Fetching & pruning origin...
            Fetching upstream changes from origin
             > git.exe --version # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --prune
            Listing remote references...
             > git.exe config --get remote.origin.url # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe ls-remote -h https://****.git # timeout=10
            Checking branches...
            {code}

            In Version 3.6.2 this happens:

            {code:none}
            Starting branch indexing...
             > git.exe --version # timeout=10
             > git.exe ls-remote --symref http://srv01.tki-chemnitz.de:82/Git/map3d-tools.git # timeout=10
            ERROR: [Mi Okt 25 14:48:06 MESZ 2017] Could not update folder level actions from source 1670125f-05be-412b-9264-27212be64b57
            hudson.plugins.git.GitException: Command "git.exe ls-remote --symref http://srv01.tki-chemnitz.de:82/Git/map3d-tools.git" returned status code 128:
            stdout:
            stderr: fatal: Authentication failed for 'http://srv01.tki-chemnitz.de:82/Git/map3d-tools.git/'

            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1924)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1643)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1561)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1552)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:2769)
            at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:804)
            at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746)
            at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591)
            at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276)
            at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)
            at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978)
            at hudson.model.ResourceController.execute(ResourceController.java:97)
            at hudson.model.Executor.run(Executor.java:421)
            {code}

            Rolling back to the old version, fixes the issue.
            The branch indexing using the git-client does not work anymore, in case the indexed repository is password protected and requires GIT_ASKPASS to be set.

            The error was introduced in the git-client 3.6.1 and my best guess is that it is related to [PR#544|https://github.com/jenkinsci/git-plugin/pull/544].

             At version 3.6.0 the branch indexing looks like this:

            {code:none}
            Starting branch indexing...
             > git.exe rev-parse --is-inside-work-tree # timeout=10
            Setting origin to http://srv01.tki-chemnitz.de:82/Git/map3d-tools.git
             > git.exe config remote.origin.url http://srv01.tki-chemnitz.de:82/Git/map3d-tools.git # timeout=10
            Fetching origin...
            Fetching upstream changes from origin
             > git.exe --version # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
            using GIT_ASKPASS to set credentials ****
             > git.exe ls-remote --symref https://****.git # timeout=10
             > git.exe rev-parse --is-inside-work-tree # timeout=10
            Setting origin to https://****.git
             > git.exe config remote.origin.url https://****.git # timeout=10
            Fetching & pruning origin...
            Fetching upstream changes from origin
             > git.exe --version # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --prune
            Listing remote references...
             > git.exe config --get remote.origin.url # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe ls-remote -h https://****.git # timeout=10
            Checking branches...
            {code}

            In Version 3.6.2 this happens:

            {code:none}
            Starting branch indexing...
             > git.exe --version # timeout=10
             > git.exe ls-remote --symref http://srv01.tki-chemnitz.de:82/Git/map3d-tools.git # timeout=10
            ERROR: [Mi Okt 25 14:48:06 MESZ 2017] Could not update folder level actions from source 1670125f-05be-412b-9264-27212be64b57
            hudson.plugins.git.GitException: Command "git.exe ls-remote --symref https://****.git" returned status code 128:
            stdout:
            stderr: fatal: Authentication failed for 'https://****.git/'

            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1924)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1643)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1561)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1552)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:2769)
            at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:804)
            at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746)
            at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591)
            at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276)
            at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)
            at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978)
            at hudson.model.ResourceController.execute(ResourceController.java:97)
            at hudson.model.Executor.run(Executor.java:421)
            {code}

            Rolling back to the old version, fixes the issue.
            nitram Martin Karing made changes -
            Description The branch indexing using the git-client does not work anymore, in case the indexed repository is password protected and requires GIT_ASKPASS to be set.

            The error was introduced in the git-client 3.6.1 and my best guess is that it is related to [PR#544|https://github.com/jenkinsci/git-plugin/pull/544].

             At version 3.6.0 the branch indexing looks like this:

            {code:none}
            Starting branch indexing...
             > git.exe rev-parse --is-inside-work-tree # timeout=10
            Setting origin to http://srv01.tki-chemnitz.de:82/Git/map3d-tools.git
             > git.exe config remote.origin.url http://srv01.tki-chemnitz.de:82/Git/map3d-tools.git # timeout=10
            Fetching origin...
            Fetching upstream changes from origin
             > git.exe --version # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
            using GIT_ASKPASS to set credentials ****
             > git.exe ls-remote --symref https://****.git # timeout=10
             > git.exe rev-parse --is-inside-work-tree # timeout=10
            Setting origin to https://****.git
             > git.exe config remote.origin.url https://****.git # timeout=10
            Fetching & pruning origin...
            Fetching upstream changes from origin
             > git.exe --version # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --prune
            Listing remote references...
             > git.exe config --get remote.origin.url # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe ls-remote -h https://****.git # timeout=10
            Checking branches...
            {code}

            In Version 3.6.2 this happens:

            {code:none}
            Starting branch indexing...
             > git.exe --version # timeout=10
             > git.exe ls-remote --symref http://srv01.tki-chemnitz.de:82/Git/map3d-tools.git # timeout=10
            ERROR: [Mi Okt 25 14:48:06 MESZ 2017] Could not update folder level actions from source 1670125f-05be-412b-9264-27212be64b57
            hudson.plugins.git.GitException: Command "git.exe ls-remote --symref https://****.git" returned status code 128:
            stdout:
            stderr: fatal: Authentication failed for 'https://****.git/'

            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1924)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1643)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1561)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1552)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:2769)
            at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:804)
            at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746)
            at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591)
            at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276)
            at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)
            at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978)
            at hudson.model.ResourceController.execute(ResourceController.java:97)
            at hudson.model.Executor.run(Executor.java:421)
            {code}

            Rolling back to the old version, fixes the issue.
            The branch indexing using the git-client does not work anymore, in case the indexed repository is password protected and requires GIT_ASKPASS to be set.

            The error was introduced in the git-client 3.6.1 and my best guess is that it is related to [PR#544|https://github.com/jenkinsci/git-plugin/pull/544].

             At version 3.6.0 the branch indexing looks like this:

            {code:none}
            Starting branch indexing...
             > git.exe rev-parse --is-inside-work-tree # timeout=10
            Setting origin to https://****.git
             > git.exe config remote.origin.url https://****.git # timeout=10
            Fetching origin...
            Fetching upstream changes from origin
             > git.exe --version # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
            using GIT_ASKPASS to set credentials ****
             > git.exe ls-remote --symref https://****.git # timeout=10
             > git.exe rev-parse --is-inside-work-tree # timeout=10
            Setting origin to https://****.git
             > git.exe config remote.origin.url https://****.git # timeout=10
            Fetching & pruning origin...
            Fetching upstream changes from origin
             > git.exe --version # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --prune
            Listing remote references...
             > git.exe config --get remote.origin.url # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe ls-remote -h https://****.git # timeout=10
            Checking branches...
            {code}

            In Version 3.6.2 this happens:

            {code:none}
            Starting branch indexing...
             > git.exe --version # timeout=10
             > git.exe ls-remote --symref http://srv01.tki-chemnitz.de:82/Git/map3d-tools.git # timeout=10
            ERROR: [Mi Okt 25 14:48:06 MESZ 2017] Could not update folder level actions from source 1670125f-05be-412b-9264-27212be64b57
            hudson.plugins.git.GitException: Command "git.exe ls-remote --symref https://****.git" returned status code 128:
            stdout:
            stderr: fatal: Authentication failed for 'https://****.git/'

            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1924)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1643)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1561)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1552)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:2769)
            at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:804)
            at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746)
            at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591)
            at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276)
            at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)
            at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978)
            at hudson.model.ResourceController.execute(ResourceController.java:97)
            at hudson.model.Executor.run(Executor.java:421)
            {code}

            Rolling back to the old version, fixes the issue.
            nitram Martin Karing made changes -
            Description The branch indexing using the git-client does not work anymore, in case the indexed repository is password protected and requires GIT_ASKPASS to be set.

            The error was introduced in the git-client 3.6.1 and my best guess is that it is related to [PR#544|https://github.com/jenkinsci/git-plugin/pull/544].

             At version 3.6.0 the branch indexing looks like this:

            {code:none}
            Starting branch indexing...
             > git.exe rev-parse --is-inside-work-tree # timeout=10
            Setting origin to https://****.git
             > git.exe config remote.origin.url https://****.git # timeout=10
            Fetching origin...
            Fetching upstream changes from origin
             > git.exe --version # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
            using GIT_ASKPASS to set credentials ****
             > git.exe ls-remote --symref https://****.git # timeout=10
             > git.exe rev-parse --is-inside-work-tree # timeout=10
            Setting origin to https://****.git
             > git.exe config remote.origin.url https://****.git # timeout=10
            Fetching & pruning origin...
            Fetching upstream changes from origin
             > git.exe --version # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --prune
            Listing remote references...
             > git.exe config --get remote.origin.url # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe ls-remote -h https://****.git # timeout=10
            Checking branches...
            {code}

            In Version 3.6.2 this happens:

            {code:none}
            Starting branch indexing...
             > git.exe --version # timeout=10
             > git.exe ls-remote --symref http://srv01.tki-chemnitz.de:82/Git/map3d-tools.git # timeout=10
            ERROR: [Mi Okt 25 14:48:06 MESZ 2017] Could not update folder level actions from source 1670125f-05be-412b-9264-27212be64b57
            hudson.plugins.git.GitException: Command "git.exe ls-remote --symref https://****.git" returned status code 128:
            stdout:
            stderr: fatal: Authentication failed for 'https://****.git/'

            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1924)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1643)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1561)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1552)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:2769)
            at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:804)
            at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746)
            at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591)
            at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276)
            at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)
            at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978)
            at hudson.model.ResourceController.execute(ResourceController.java:97)
            at hudson.model.Executor.run(Executor.java:421)
            {code}

            Rolling back to the old version, fixes the issue.
            The branch indexing using the git-client does not work anymore, in case the indexed repository is password protected and requires GIT_ASKPASS to be set.

            The error was introduced in the git-client 3.6.1 and my best guess is that it is related to [PR#544|https://github.com/jenkinsci/git-plugin/pull/544].

             At version 3.6.0 the branch indexing looks like this:

            {code:none}
            Starting branch indexing...
             > git.exe rev-parse --is-inside-work-tree # timeout=10
            Setting origin to https://****.git
             > git.exe config remote.origin.url https://****.git # timeout=10
            Fetching origin...
            Fetching upstream changes from origin
             > git.exe --version # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
            using GIT_ASKPASS to set credentials ****
             > git.exe ls-remote --symref https://****.git # timeout=10
             > git.exe rev-parse --is-inside-work-tree # timeout=10
            Setting origin to https://****.git
             > git.exe config remote.origin.url https://****.git # timeout=10
            Fetching & pruning origin...
            Fetching upstream changes from origin
             > git.exe --version # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --prune
            Listing remote references...
             > git.exe config --get remote.origin.url # timeout=10
            using GIT_ASKPASS to set credentials ****
             > git.exe ls-remote -h https://****.git # timeout=10
            Checking branches...
            {code}

            In Version 3.6.2 this happens:

            {code:none}
            Starting branch indexing...
             > git.exe --version # timeout=10
             > git.exe ls-remote --symref https://****.git # timeout=10
            ERROR: [Mi Okt 25 14:48:06 MESZ 2017] Could not update folder level actions from source 1670125f-05be-412b-9264-27212be64b57
            hudson.plugins.git.GitException: Command "git.exe ls-remote --symref https://****.git" returned status code 128:
            stdout:
            stderr: fatal: Authentication failed for 'https://****.git/'

            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1924)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1643)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1561)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1552)
            at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:2769)
            at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:804)
            at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746)
            at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591)
            at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276)
            at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)
            at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978)
            at hudson.model.ResourceController.execute(ResourceController.java:97)
            at hudson.model.Executor.run(Executor.java:421)
            {code}

            Rolling back to the old version, fixes the issue.
            Hide
            markewaite Mark Waite added a comment - - edited

            Can you provide more details so that I can duplicate the problem?

            I've confirmed in my installations that git plugin 3.6.2 scans a private multi-branch pipeline with command line git using git 2.11 and a private https based repository with git as the branch source, github as the branch source, and bitbucket as the branch source.

            Here's what I think I've confirmed from your description and log:

            • Repository protocol: https (not ssh)
            • Credentials: username / password (not private key)
            • Job: multi-branch pipeline (not freestyle, not single pipeline)
            • Git implementation: command line git (not jgit, not jgit-apache)
            • Operating system: Windows (my tests were run on Linux in a Docker container)

            Things that aren't clear:

            • Repository hosting provider: (I've checked github and bitbucket)
            • Command line git version:
            • Other: Special conditions that may exist in your job definition or your environment (for example, are you using self-signed certificates)
            Show
            markewaite Mark Waite added a comment - - edited Can you provide more details so that I can duplicate the problem? I've confirmed in my installations that git plugin 3.6.2 scans a private multi-branch pipeline with command line git using git 2.11 and a private https based repository with git as the branch source, github as the branch source, and bitbucket as the branch source. Here's what I think I've confirmed from your description and log: Repository protocol : https (not ssh) Credentials : username / password (not private key) Job : multi-branch pipeline (not freestyle, not single pipeline) Git implementation : command line git (not jgit, not jgit-apache) Operating system : Windows (my tests were run on Linux in a Docker container) Things that aren't clear: Repository hosting provider : (I've checked github and bitbucket) Command line git version : Other : Special conditions that may exist in your job definition or your environment (for example, are you using self-signed certificates)
            Hide
            nitram Martin Karing added a comment -
            • Repository Protocol: http
            • Credentials: username / password
            • Job: Multi-Branch Pipeline
            • Git implementation: command line git
            • Operating System: Windows Server 2012 R2
            • Repository Hosting Provider: Bonobo Git-Server 5.2 (https://bonobogitserver.com/)
            • Git Version: 2.14.3.windows.1
            • Other: The git server is authenticating using an active directory server. But from the perspective of git it should receive a simple http basic authentication request.
            Show
            nitram Martin Karing added a comment - Repository Protocol: http Credentials: username / password Job : Multi-Branch Pipeline Git implementation : command line git Operating System: Windows Server 2012 R2 Repository Hosting Provider : Bonobo Git-Server 5.2 ( https://bonobogitserver.com/ ) Git Version : 2.14.3.windows.1 Other : The git server is authenticating using an active directory server. But from the perspective of git it should receive a simple http basic authentication request.
            Hide
            markewaite Mark Waite added a comment - - edited

            Martin Karing thanks for the additional details. Were there any other changes in your environment which might be involved?

            Have you bisected the plugin changes between the working and the non-working state to identify the specific commit, or is your suggestion of PR544 an educated guess? I don't see anything in PR544 which should alter the authentication used by the plugin. Stephen Connolly may have a better assessment than I do of possible credential related side effects in that pull request

            If you haven't bisiected the changes, would you be willing to do that? If you're not comfortable compiling the plugin for each of the commits, I can provide compiled versions of the plugin for you to use. I can't duplicate the problem, and am not willing to install and configure Bonobo Git Server, since I don't have a Windows Server license and my Windows client machines don't have IIS installed.

            Also, you flagged in your comments that you're using http protocoi, yet the log shows https protocol. Can you clarify if you're using http or https protocol to access the repo?

            Show
            markewaite Mark Waite added a comment - - edited Martin Karing thanks for the additional details. Were there any other changes in your environment which might be involved? Have you bisected the plugin changes between the working and the non-working state to identify the specific commit, or is your suggestion of PR544 an educated guess? I don't see anything in PR544 which should alter the authentication used by the plugin. Stephen Connolly may have a better assessment than I do of possible credential related side effects in that pull request If you haven't bisiected the changes, would you be willing to do that? If you're not comfortable compiling the plugin for each of the commits, I can provide compiled versions of the plugin for you to use. I can't duplicate the problem, and am not willing to install and configure Bonobo Git Server, since I don't have a Windows Server license and my Windows client machines don't have IIS installed. Also, you flagged in your comments that you're using http protocoi, yet the log shows https protocol. Can you clarify if you're using http or https protocol to access the repo?
            Hide
            nitram Martin Karing added a comment -

            It was a educated guess I made based on all the changes that were reported in the logs.

            The protocol that is in use is http.
            I will bisect the commits since the last version to identify the issue. I get back to you with the results.

            Show
            nitram Martin Karing added a comment - It was a educated guess I made based on all the changes that were reported in the logs. The protocol that is in use is http . I will bisect the commits since the last version to identify the issue. I get back to you with the results.
            markewaite Mark Waite made changes -
            Environment git-client: 3.6.2
            Jenkins: 2.86
            Windows Server 2012 R2
            git-plugin: 3.6.2
            Jenkins: 2.86
            Windows Server 2012 R2
            Hide
            nitram Martin Karing added a comment -

            Bisecting result:

            Bisecting: 0 revisions left to test after this (roughly 0 steps)
            [3b516c331b42518570c4d57345d198f44ee05070] These two operations do not actually need the local repository cache
            

            This is the commit breaking it.

            Show
            nitram Martin Karing added a comment - Bisecting result: Bisecting: 0 revisions left to test after this (roughly 0 steps) [3b516c331b42518570c4d57345d198f44ee05070] These two operations do not actually need the local repository cache This is the commit breaking it.
            Hide
            lukelast Luke Last added a comment -

            I hit this bug also using SSH key based credentials. Reverting back to 2.6.0 got it working again.

             

            > git ls-remote --symref git@xxxxx.git # timeout=10
            ERROR: [Wed Oct 25 18:46:01 EDT 2017] Could not update folder level actions from source xxxxxx
            hudson.plugins.git.GitException: Command "git ls-remote --symref git@xxxxxxx.git" returned status code 128:
            stdout: 
            stderr: Permission denied (publickey).
            fatal: Could not read from remote repository.
            
            Please make sure you have the correct access rights
            and the repository exists.
            
            	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1924)
            	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1643)
            	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1561)
            	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1552)
            	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:2769)
            	at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:804)
            	at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746)
            	at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591)
            	at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276)
            	at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)
            	at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978)
            	at hudson.model.ResourceController.execute(ResourceController.java:97)
            	at hudson.model.Executor.run(Executor.java:421)
            Show
            lukelast Luke Last added a comment - I hit this bug also using SSH key based credentials. Reverting back to 2.6.0 got it working again.   > git ls-remote --symref git@xxxxx.git # timeout=10 ERROR: [Wed Oct 25 18:46:01 EDT 2017] Could not update folder level actions from source xxxxxx hudson.plugins.git.GitException: Command "git ls-remote --symref git@xxxxxxx.git" returned status code 128: stdout: stderr: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1924) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1643) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1561) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1552) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:2769) at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:804) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:421)
            markewaite Mark Waite made changes -
            Link This issue is duplicated by JENKINS-47659 [ JENKINS-47659 ]
            Hide
            markewaite Mark Waite added a comment -

            Martin Karing and Luke Last thanks for the feedback. I'll work with Stephen Connolly to either repair or revert the issue in the commit.

            I still can't duplicate the problem. Since the revert of that commit is non-trivial (now mixed with later changes), I'll want to be able to duplicate the problem before releasing a plugin version with the fix.

            Show
            markewaite Mark Waite added a comment - Martin Karing and Luke Last thanks for the feedback. I'll work with Stephen Connolly to either repair or revert the issue in the commit . I still can't duplicate the problem. Since the revert of that commit is non-trivial (now mixed with later changes), I'll want to be able to duplicate the problem before releasing a plugin version with the fix.
            Hide
            stephenconnolly Stephen Connolly added a comment -

            I think https://github.com/jenkinsci/git-plugin/pull/548 should fix the issue (it was an E_NOT_ENOUGH_COPY_PASTE error code )

            Show
            stephenconnolly Stephen Connolly added a comment - I think https://github.com/jenkinsci/git-plugin/pull/548  should fix the issue (it was an E_NOT_ENOUGH_COPY_PASTE error code  )
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Stephen Connolly
            Path:
            src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java
            http://jenkins-ci.org/commit/git-plugin/254ad49d933015d842bd839dae567d399a275b88
            Log:
            [FIXED JENKINS-47629] Forgot to apply the credentials in the short-cut

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java http://jenkins-ci.org/commit/git-plugin/254ad49d933015d842bd839dae567d399a275b88 Log: [FIXED JENKINS-47629] Forgot to apply the credentials in the short-cut
            scm_issue_link SCM/JIRA link daemon made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Mark Waite
            Path:
            src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java
            http://jenkins-ci.org/commit/git-plugin/12a389b461320ae4665622ceccce4c3c76fecfee
            Log:
            Merge pull request #548 from stephenc/jenkins-47629

            [FIXED JENKINS-47629] Forgot to apply the credentials in the short-cut

            Compare: https://github.com/jenkinsci/git-plugin/compare/6f485761657f...12a389b46132

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Mark Waite Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java http://jenkins-ci.org/commit/git-plugin/12a389b461320ae4665622ceccce4c3c76fecfee Log: Merge pull request #548 from stephenc/jenkins-47629 [FIXED JENKINS-47629] Forgot to apply the credentials in the short-cut Compare: https://github.com/jenkinsci/git-plugin/compare/6f485761657f...12a389b46132
            Hide
            markewaite Mark Waite added a comment -

            Martin Karing and Luke Last could you download the build and test it with your case?

            The git.hpi file from those artifacts needs to be uploaded to your Jenkins server through the "Managed Plugins" link, under "Advanced".

            Show
            markewaite Mark Waite added a comment - Martin Karing and Luke Last could you download the build and test it with your case? The git.hpi file from those artifacts needs to be uploaded to your Jenkins server through the "Managed Plugins" link, under "Advanced".
            Hide
            bv2017 Björn Voß added a comment -

            Mark Waite I ran in the exact same problem and the snapshot fixed it.

            A fast bugfix release would be great

            Show
            bv2017 Björn Voß added a comment - Mark Waite I ran in the exact same problem and the snapshot fixed it. A fast bugfix release would be great
            Hide
            markewaite Mark Waite added a comment -

            Thanks for helping Björn Voß. I'll create the release.

            Show
            markewaite Mark Waite added a comment - Thanks for helping Björn Voß . I'll create the release.
            Hide
            markewaite Mark Waite added a comment -

            Included in git plugin 3.6.3 released 26 Oct 2017

            Show
            markewaite Mark Waite added a comment - Included in git plugin 3.6.3 released 26 Oct 2017
            markewaite Mark Waite made changes -
            Link This issue is duplicated by JENKINS-47680 [ JENKINS-47680 ]
            Hide
            nitram Martin Karing added a comment -

            git plugin version 3.6.3 works again. Good job Stephen Connolly.

            Show
            nitram Martin Karing added a comment - git plugin version 3.6.3 works again. Good job Stephen Connolly .
            Hide
            lukelast Luke Last added a comment -

            Yay fixed!

            Show
            lukelast Luke Last added a comment - Yay fixed!
            markewaite Mark Waite made changes -
            Status Resolved [ 5 ] Closed [ 6 ]

              People

              • Assignee:
                markewaite Mark Waite
                Reporter:
                nitram Martin Karing
              • Votes:
                6 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: