[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-38860 Git plugin using local config to update submodules Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Mark Waite updated JENKINS-38860 Jenkins / JENKINS-38860 Git plugin using local config to update submodules Change By: Mark Waite Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Rafal Janicki commented on JENKINS-38860 Re: Git plugin using local config to update submodules Unfortunately, I ran into the exact issue as described by Chris Kitching. I tried to disable the recursive option of checking out, but that didn't work either - the plugin still tries to clone recursively. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title kboz commented on JENKINS-38860 Re: Git plugin using local config to update submodules Still happening in git plugin 3.1.0 with git-client 2.3.0 git config --get-regexp is referencing the committed .gitmodules config file, but then git config --get is not. If the reference is present in the repo, but not locally, it fails with status code 1 such as below. Adding -f .gitmodules to the second command as well would work. > git submodule init # timeout=10 > git config -f .gitmodules --get-regexp ^submodule\.(.*)\.url # timeout=10 > git config --get submodule.rake-tasks.url # timeout=10 FATAL: Command "git config --get submodule.rake-tasks.url" returned status code 1: stdout: stderr: hudson.plugins.git.GitException: Command "git config --get submodule.rake-tasks.url" returned status code 1: stdout: stderr: at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1793) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1766) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1762) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1409) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1421) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getSubmoduleUrl(CliGitAPIImpl.java:1091) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1017) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:102) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1156) at hudson.scm.SCM.checkout(SCM.java:496) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:405) Add Comment
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Pierre Larsson updated an issue Jenkins / JENKINS-38860 Git plugin using local config to update submodules Change By: Pierre Larsson Environment: Jenkins v2.6, Git plugin version 3.0.0, git-client 2. 0 2 . 0 1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Pierre Larsson reopened an issue Happening again in 2.2.1. I downgraded all the plugins and now it's working again. Try cloning g...@github.com:bbcarchdev/acropolis.git with enabled recursive in jenkins. Error message > git config --get submodule.twine-anansi-bridge/m4.url # timeout=10 FATAL: Command "git config --get submodule.twine-anansi-bridge/m4.url" returned status code 1: stdout: stderr: hudson.plugins.git.GitException: Command "git config --get submodule.twine-anansi-bridge/m4.url" returned status code 1: stdout: stderr: at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1784) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1757) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1753) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1409) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1421) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getSubmoduleUrl(CliGitAPIImpl.java:1091) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1017) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ..remote call to centos7_slave (i-0c8cc1000943d412e)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:822) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) at sun.reflect.GeneratedMethodAccessor151.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131) at com.sun.proxy.$Proxy65.execute(Unknown Source) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:90) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1141) at hudson.scm.SCM.checkout(SCM.java:496) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:405) Finished: FAILURE
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Mark Waite resolved as Fixed Jenkins / JENKINS-38860 Git plugin using local config to update submodules Change By: Mark Waite Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Mark Waite commented on JENKINS-38860 Re: Git plugin using local config to update submodules Fixed in git client plugin 2.2.0, released 2 Jan 2017 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-38860 Git plugin using local config to update submodules Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Sam Deane commented on JENKINS-38860 Re: Git plugin using local config to update submodules > It's like this plugin wasn't tested before going live Indeed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Roman Karlstetter commented on JENKINS-38860 Re: Git plugin using local config to update submodules In my experience, running git submodule deinit . (for example as a pre-scm-build-step) does not work. What works for me: remove advanced submodule behavior git submodule deinit . as pre-scm build-step (this is optional, might not be necessary) git submodule update --init as first build step after checkout Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Senthilkumar Palanisamy commented on JENKINS-38860 Re: Git plugin using local config to update submodules We have checked this option "Recursively update submodules" in job configuration page. Where we have to mention the command "git submodule deinit" please can you correct me. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Boris Danilovich commented on JENKINS-38860 Re: Git plugin using local config to update submodules You can run "git submodule deinit" on the repo on your jenkins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Senthilkumar Palanisamy commented on JENKINS-38860 Re: Git plugin using local config to update submodules Hi, Please can i know is there any other work around to fix this issue "stderr: error: pathspec 'ProjectA/testrepo' did not match any file(s) known to git." This is really blocking our all builds. As of now we are wiping out our workspace to ignore this error every time. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title
Roman Karlstetter edited a comment on JENKINS-38860
Re: Git plugin using local config to update submodules
I can confirm this issue. It happened to us after the update of the git-plugin to version 3.0.0. 'git submodule update --init' always worked fine for us.This is the error we are getting:{code:none}> C:\Program Files\Git\bin\git.exe submodule update --init --recursive old_path/to/subFATAL: Command "C:\Program Files\Git\bin\git.exe submodule update --init --recursive old_path/to/sub" returned status code 1:stdout: stderr: error: pathspec 'old_path/to/sub' did not match any file(s) known to git.hudson.plugins.git.GitException: Command "C:\Program Files\Git\bin\git.exe submodule update --init --recursive old_path/to/sub" returned status code 1:stdout: stderr: error: pathspec 'old_path/to/sub' did not match any file(s) known to git. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1032) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:96) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1137) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:313) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404){code}One thing to note: it uses {{old_path/to/sub}} instead of the actual new path. In .gitmodules, "old_path/to/sub" is just still the name of the submodules submodule , so it tries to use the name instead of the actually configured submodule path.
Add Comment
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title
Roman Karlstetter edited a comment on JENKINS-38860
Re: Git plugin using local config to update submodules
I can confirm this issue. It happened to us after the update of the git-plugin to version 3.0.0. 'git submodule update --init' always worked fine for us.This is the error we are getting:{code:none}> C:\Program Files\Git\bin\git.exe submodule update --init --recursive old_path/to/subFATAL: Command "C:\Program Files\Git\bin\git.exe submodule update --init --recursive old_path/to/sub" returned status code 1:stdout: stderr: error: pathspec 'old_path/to/sub' did not match any file(s) known to git.hudson.plugins.git.GitException: Command "C:\Program Files\Git\bin\git.exe submodule update --init -- recursiveold_path recursive old_path /to/sub" returned status code 1:stdout: stderr: error: pathspec 'old_path/to/sub' did not match any file(s) known to git. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1032) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:96) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1137) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:313) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404){code}One thing to note: it uses {{old_path/to/sub}} instead of the actual new path. In .gitmodules, "old_path/to/sub" is just still the name of the submodules, so it tries to use the name instead of the actually configured submodule path.
Add Comment
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title
Roman Karlstetter edited a comment on JENKINS-38860
Re: Git plugin using local config to update submodules
I can confirm this issue. It happened to us after the update of the git-plugin to version 3.0.0. 'git submodule update --init' always worked fine for us.This is the error we are getting:{code: shell none }> C:\Program Files\Git\bin\git.exe submodule update --init --recursive old_path/to/subFATAL: Command "C:\Program Files\Git\bin\git.exe submodule update --init --recursive old_path/to/sub" returned status code 1:stdout: stderr: error: pathspec 'old_path/to/sub' did not match any file(s) known to git.hudson.plugins.git.GitException: Command "C:\Program Files\Git\bin\git.exe submodule update --init --recursiveold_path/to/sub" returned status code 1:stdout: stderr: error: pathspec 'old_path/to/sub' did not match any file(s) known to git. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1032) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:96) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1137) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:313) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404){code}One thing to note: it uses {{old_path/to/sub}} instead of the actual new path. In .gitmodules, "old_path/to/sub" is just still the name of the submodules, so it tries to use the name instead of the actually configured submodule path.
Add Comment
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title
Roman Karlstetter edited a comment on JENKINS-38860
Re: Git plugin using local config to update submodules
I can confirm this issue. It happened to us after the update of the git-plugin to version 3.0.0. 'git submodule update --init' always worked fine for us.This is the error we are getting: { { code:shell} > C:\Program Files\Git\bin\git.exe submodule update --init --recursive old_path/to/subFATAL: Command "C:\Program Files\Git\bin\git.exe submodule update --init --recursive old_path/to/sub" returned status code 1:stdout: stderr: error: pathspec 'old_path/to/sub' did not match any file(s) known to git.hudson.plugins.git.GitException: Command "C:\Program Files\Git\bin\git.exe submodule update --init --recursiveold_path/to/sub" returned status code 1:stdout: stderr: error: pathspec 'old_path/to/sub' did not match any file(s) known to git. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1032) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:96) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1137) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:313) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) {code } } One thing to note: it uses {{old_path/to/sub}} instead of the actual new path. In .gitmodules, "old_path/to/sub" is just still the name of the submodules, so it tries to use the name instead of the actually configured submodule path.
Add Comment
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title
Roman Karlstetter edited a comment on JENKINS-38860
Re: Git plugin using local config to update submodules
I can confirm this issue. It happened to us after the update of the git-plugin to version 3.0.0. 'git submodule update --init' always worked fine for us.This is the error we are getting:{{ > C:\Program Files\Git\bin\git.exe submodule update --init --recursive old_path/to/subFATAL: Command "C:\Program Files\Git\bin\git.exe submodule update --init --recursive old_path/to/sub" returned status code 1:stdout: stderr: error: pathspec 'old_path/to/sub' did not match any file(s) known to git.hudson.plugins.git.GitException: Command "C:\Program Files\Git\bin\git.exe submodule update --init --recursiveold_path/to/sub" returned status code 1:stdout: stderr: error: pathspec 'old_path/to/sub' did not match any file(s) known to git. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1032) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:96) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1137) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:313) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) }}One thing to note: it uses {{old_path/to/sub}} instead of the actual new path. In .gitmodules, "old_path/to/sub" is just still the name of the submodules, so it tries to use the name instead of the actually configured submodule path.
Add Comment
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title
Roman Karlstetter edited a comment on JENKINS-38860
Re: Git plugin using local config to update submodules
I can confirm this issue. It happened to us after the update of the git-plugin to version 3.0.0. 'git submodule update --init' always worked fine for us. This is the error we are getting:{{ > C:\Program Files\Git\bin\git.exe submodule update --init --recursive old_path/to/subFATAL: Command "C:\Program Files\Git\bin\git.exe submodule update --init --recursive old_path/to/sub" returned status code 1:stdout: stderr: error: pathspec 'old_path/to/sub' did not match any file(s) known to git.hudson.plugins.git.GitException: Command "C:\Program Files\Git\bin\git.exe submodule update --init --recursiveold_path/to/sub" returned status code 1:stdout: stderr: error: pathspec 'old_path/to/sub' did not match any file(s) known to git. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1032) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:96) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1137) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:313) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)}}One thing to note: it uses {{old_path/to/sub}} instead of the actual new path. In .gitmodules, "old_path/to/sub" is just still the name of the submodules, so it tries to use the name instead of the actually configured submodule path.
Add Comment
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Roman Karlstetter commented on JENKINS-38860 Re: Git plugin using local config to update submodules I can confirm this issue. It happened to us after the update of the git-plugin to version 3.0.0. 'git submodule update --init' always worked fine for us. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Kaveh Vaghefi commented on JENKINS-38860 Re: Git plugin using local config to update submodules The workaround is to downgrade the git-plugin and git-client to the previous revision. I have to ask, why is the submodule update being done like this anyway? What was wrong with 'git submodule update --init'? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Lars Hagström commented on JENKINS-38860 Re: Git plugin using local config to update submodules I'm not enough of a git guru to understand exactly what is happening here, but I believe I am being bitten by this issue. Cannot get any builds working Does anyone have a workaround? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Kaveh Vaghefi updated an issue Jenkins / JENKINS-38860 Git plugin using local config to update submodules Change By: Kaveh Vaghefi Environment: Jenkins v2.6, Git plugin version 3.0.0 , git-client 2.0.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Kaveh Vaghefi edited a comment on JENKINS-38860 Re: Git plugin using local config to update submodules I'm running into this too. This is a huge regression from where the plugin was at. It's like this plugin wasn't tested before going live. I think this is a git-client issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Kaveh Vaghefi edited a comment on JENKINS-38860 Re: Git plugin using local config to update submodules I'm running into this too. This is a huge regression from where the plugin was at. It's like it this plugin wasn't tested before going live. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Kaveh Vaghefi updated an issue Jenkins / JENKINS-38860 Git plugin using local config to update submodules Change By: Kaveh Vaghefi Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Kaveh Vaghefi commented on JENKINS-38860 Re: Git plugin using local config to update submodules I'm running into this too. This is a huge regression from where the plugin was at. It's like it this plugin wasn't tested before going live. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-38860 Git plugin using local config to update submodules Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Boris Danilovich created an issue Jenkins / JENKINS-38860 Git plugin using local config to update submodules Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Oct/10 12:55 PM Environment: Jenkins v2.6, Git plugin version 3.0.0 Priority: Major Reporter: Boris Danilovich In order to get all of the submodules, the git plugin looks in the local configuration file: > git config --get-regexp ^submodule # timeout=10 > git config --get submodule.externals/jzmq.url # timeout=10 > git submodule update --remote externals/jzmq > git config --get submodule.protobuf-java-format.url # timeout=10 > git submodule update --remote protobuf-java-format FATAL: Command "git submodule update --remote protobuf-java-format" returned status code 1: stdout: stderr: error: pathspec 'protobuf-java-format' did not match any file(s) known to git. However, the .git/config file is local per repository, and old entries and sections do not get overriden. Therefore, when a submodule is no longer in use or has moved, the old configuration can cause an error. Anyway, the local configuration is not part of the remote repository, which is the correct clean repo which is the exclusive authority on git configs. A possible solution would be to call deninit in order to remove the old configuration.
