-
Bug
-
Resolution: Not A Defect
-
Blocker
-
None
-
latest Jenkins LTS Jenkins ver. 2.222.1
git plugin
multi branch pipeline
need proxy to use SCM (bitbucket)
have update from Jenkins LTS Jenkins ver. 2.204.5 to the latest LTS: Jenkins ver. 2.222.1
now my git multi branch pipeline through proxy doesn't work anymore
with Jenkins ver. 2.204.5 it was working fine:
Started by user testuser [Thu Mar 26 14:22:58 CET 2020] Starting branch indexing... > git.exe --version # timeout=10 using GIT_ASKPASS to set credentials Setting http proxy: proxy.*****.com:8080 > git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git # timeout=10 ERROR: [Thu Mar 26 14:22:58 CET 2020] Could not update folder level actions from source 4ad1ee05-7f07-477a-a003-aa5b11127210 hudson.plugins.git.GitException: Command "git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git" returned status code 128: stdout: stderr: fatal: unable to access 'https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git/': Received HTTP code 407 from proxy after CONNECT at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1944) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1935) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:3360) at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:1121) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:848) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:598) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1032) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428) [Thu Mar 26 14:22:58 CET 2020] Finished branch indexing. Indexing took 0.5 sec FATAL: Failed to recompute children of Infrastructure hudson.plugins.git.GitException: Command "git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git" returned status code 128: stdout: stderr: fatal: unable to access 'https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git/': Received HTTP code 407 from proxy after CONNECT at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1944) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1935) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:3360) at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:1121) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:848) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:598) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1032) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428) Finished: FAILURE
- relates to
-
JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
-
- Resolved
-
Based on the bug report that you linked (
JENKINS-61692), I would guess that the proxy settings are not defined, since the validation failed with an NPE.If you're willing to experiment, you could try inserting the proxy definition from the working Jenkins configuration files of 2.204.5 into the XML config files of Jenkins 2.222.1. That might avoid the validation failure and assure that a proxy is defined.