[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59794 Using a period as the branch name in .gitModules does not work. Change By: Mark Waite Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202524.1571167644000.10292.1573072620260%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Jon Roberts commented on JENKINS-59794 Re: Using a period as the branch name in .gitModules does not work. Actually looking at my stacktrace again I noticed it's not a windows path and forgot this was running on a linux agent. That agent has git 2.7.4. I'll hold out some hope since it looks like it's just running straight up git. /usr/bin/git submodule update --init --recursive --remote curavi-common" returned status code 1: Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202524.1571167644000.10268.1573068120122%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Mark Waite commented on JENKINS-59794 Re: Using a period as the branch name in .gitModules does not work. Jon Roberts I don't expect it to work with the Jenkins git plugin. The Jenkins git plugin performs git submodule operations in its own distinct way. One of the differences from the most recent command line git versions is likely the handling of the '.' special case. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202524.1571167644000.10261.1573067580154%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Jon Roberts commented on JENKINS-59794 Re: Using a period as the branch name in .gitModules does not work. That's good to know. I'm running 2.16.2 on windows, so it should work. I'll update to the latest and give it a shot to see if that fixes it once I get a chance. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202524.1571167644000.10259.1573067220200%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Mark Waite commented on JENKINS-59794 Re: Using a period as the branch name in .gitModules does not work. The special value of '.' depends on command line git 2.10 or later (at least according to the documentation at https://git-scm.com/docs/git-submodule/2.10.2 and at https://git-scm.com/docs/git-submodule/2.9.0 . If this is implemented, it will need to be safeguarded so that it is only used if the CLI git version is new enough to support it. Many popular operating systems do no ship git 2.10 or newer (CentOS 6,. CentOS 7, Ubuntu 16.04) and the plugins generally try to not break those older versions. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202524.1571167644000.6496.1572557940132%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59794 Using a period as the branch name in .gitModules does not work. Change By: Mark Waite Labels: submodules Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202524.1571167644000.8331.1571174400607%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59794 Using a period as the branch name in .gitModules does not work. Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202524.1571167644000.8333.1571174400707%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Jon Roberts created an issue Jenkins / JENKINS-59794 Using a period as the branch name in .gitModules does not work. Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-10-15 19:27 Priority: Minor Reporter: Jon Roberts When you specify the branch name as a '.' (period) in .gitModules you should be able to use the --remote option to update submodules to the head the branch that matches the parent branch. When doing this in Jenkins we get the following error: hudson.plugins.git.GitException: Command "/usr/bin/git submodule update --init --recursive --remote curavi-common" returned status code 1: stdout: stderr: Cloning into 'curavi-common'... fatal: Needed a single revision Unable to find current origin/. revision in submodule path 'curavi-common' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1202) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadP
