[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 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 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
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Jon Roberts commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace As a workaround for this had to write a cron job that scans the get branches, matches them up with the workspace folders, then removes them. An option that would just do then whenever the job is removed would be fantastic. 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-49434) Multibranch pipeline doesn't trigger on Git submodule changes
Title: Message Title Jon Roberts commented on JENKINS-49434 Re: Multibranch pipeline doesn't trigger on Git submodule changes We have a similar setup. We have our develop parent branch tracking the tip of develop submodules. In Jenkins I had to setup watch jobs that monitor the develop submodules for changes then kick off the parent develop build. All that works great. Now I'm trying to figure out how to do something similar with a multibranch pipeline. It'd be great if I could somehow monitor the submodule projects then kick off the the parent project again, but specify which submodule branches to checkout. I think you can setup multiple sources for your submodule projects. The the Jenkinsfile would then have to checkout the parent project and build all the things. Probably would need to duplicate/have similar jenkinsfiles in each submodule, since they would all have to know how to build themselves from the parent. 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Jon Roberts commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Nevermind! I was able to update the the submodule path in .gitmodule a relative path to get them to clone. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Jon Roberts commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Yes, thanks that looks like my issue. Any easy way to override the url of the submodule for this jenkins instance? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Jon Roberts commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated I'm still having trouble with this bug even with the 1.20.0-beta3 update. I'm using an http repo with a username and password login. It looks like it's trying to use the credentials but still fails: using GIT_ASKPASS to set credentials Gitlab Jenkins User > git submodule update --init --recursive libraries FATAL: Command "git submodule update --init --recursive libraries" returned status code 1: stdout: stderr: Cloning into 'libraries'... Permission denied (publickey). fatal: Could not read from remote repository. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
