[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service
Mark Waite updated JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service Change By: Mark Waite (12/Oct/14 2:43 AM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service
Mark Waite updated JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service Change By: Mark Waite (06/Feb/14 5:05 AM) Summary: GitCLIcannotcloneonWindowsusingGIT_SSHtosetcredentials whenrunningasaservice This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Mark Waite commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials I was able to confirm Hallvard's report that when running Jenkins as a service, it is unable to checkout if the Git URL uses ssh:// (like ssh://wheezy64/var/lib/git/mwaite/bin.git ). I am still able to checkout if the Git URL uses ssh protocol without the ssh:(like g...@github.com:MarkEWaite/jenkins-demo.git ). I am still able to checkout if Jenkins is not running as a service, even when it uses an ssh:// URL. It requires both that it is running as a service and that it is using ssh: protocol. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Hallvard Nygård commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Upgraded Jenkins GIT client plugin to 1.6.0. Started getting the following output: Building in workspace D:\Jenkins\jobs\Project\workspace Fetching changes from the remote Git repository Fetching upstream changes from ssh://jenkins@gerrit:29418/Project.git using GIT_SSH to set credentials -- Killed it after 6 minutes. Then the following output: FATAL: Failed to fetch from ssh://jenkins@gerrit:29418/Project.git hudson.plugins.git.GitException: Failed to fetch from ssh://jenkins@gerrit:29418/Project.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:612) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:836) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861) at hudson.model.AbstractProject.checkout(AbstractProject.java:1412) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) at hudson.model.Run.execute(Run.java:1679) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Caused by: hudson.plugins.git.GitException: Error performing git command at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1108) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:985) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:69) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:218) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:224) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:229) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:610) ... 10 more Caused by: java.lang.InterruptedException at java.lang.ProcessImpl.waitFor(Unknown Source) at hudson.Proc$LocalProc.join(Proc.java:319) at hudson.Proc.joinWithTimeout(Proc.java:168) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1095) ... 16 more Last build before upgrade had the following output related to Git: Building in workspace D:\Jenkins\jobs\Project\workspace@2 Fetching changes from the remote Git repository Fetching upstream changes from ssh://jenkins@gerrit:29418/Project.git Checking out Revision bbb4481de2d3f8eb16d5dbf9f5a992c24eb4f1ed (master) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Hallvard Nygård reopened JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Change By: Hallvard Nygård (20/Dec/13 8:10 AM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Hallvard Nygård edited a comment on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Upgraded Jenkins GIT client plugin to 1.6.0. Running Jenkins as Windows service on Windows Server 2012 Started getting the following output: Building in workspace D:\Jenkins\jobs\Project\workspace Fetching changes from the remote Git repository Fetching upstream changes from ssh://jenkins@gerrit:29418/Project.git using GIT_SSH to set credentials -- Killed it after 6 minutes. Then the following output: FATAL: Failed to fetch from ssh://jenkins@gerrit:29418/Project.git hudson.plugins.git.GitException: Failed to fetch from ssh://jenkins@gerrit:29418/Project.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:612) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:836) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861) at hudson.model.AbstractProject.checkout(AbstractProject.java:1412) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) at hudson.model.Run.execute(Run.java:1679) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Caused by: hudson.plugins.git.GitException: Error performing git command at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1108) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:985) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:69) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:218) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:224) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:229) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:610) ... 10 more Caused by: java.lang.InterruptedException at java.lang.ProcessImpl.waitFor(Unknown Source) at hudson.Proc$LocalProc.join(Proc.java:319) at hudson.Proc.joinWithTimeout(Proc.java:168) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1095) ... 16 more Last build before upgrade had the following output related to Git: Building in workspace D:\Jenkins\jobs\Project\workspace@2 Fetching changes from the remote Git repository Fetching upstream changes from ssh://jenkins@gerrit:29418/Project.git Checking out Revision bbb4481de2d3f8eb16d5dbf9f5a992c24eb4f1ed (master) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Hallvard Nygård commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Downgraded "Git Client Plugin" to 1.4.5 and it worked fine again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Mark Waite commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Git client plugin 1.5.0 has released. I plan to confirm this bug is fixed in that version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Mark Waite
updated JENKINS-20356
Git CLI cannot clone on Windows using GIT_SSH to set credentials
Change By:
Mark Waite
(17/Dec/13 2:38 AM)
Description:
AgitjobconfiguredtousethecommandlineimplementationwithGitplugin2.0andgitclientplugin1.4.6failstocloneonWindows,butsuccessfullyclonesonLinux.Theproblemseemstobethatitistryingtoconfigureanenvironment(settingSSH_PASS=echo)forthelaunchedcommand,eventhoughWindowsdoesnotusethesametechniquetopassenvironmentvariablestoaprocess.Ithinktherewasadifferentbehaviorinpriorversionsofgit-client.Icreatedthejobby:
0-
#
Configureaglobalsshcredential
1-
#
Createanewjob,restrictittoonlyrunonWindows
2-
#
UseagitsshprotocolURL(likessh://wheezy64b/var/cache/git/mwaite/bin.git)
3-
#
Selectthecorrectsshcredentialfromthedropdownlist
4-
#
Addabuildstep(IusedXShellechohelloworld)
5-
#
Savethejob
6-
#
RunthejobStacktraceonWindows:
{noformat}
StartedbyuseranonymousBuildingremotelyonalan-pcinworkspaceC:\J\workspace\git-cli-sshCloningtheremoteGitrepositoryCloningrepositoryssh://wheezy64b/var/cache/git/mwaite/bin.gitgit--versiongitversion1.8.3.msysgit.0usingGIT_SSHtosetcredentialsJenkinsERROR:Errorcloningremoterepooriginhudson.plugins.git.GitException:Couldnotclonessh://wheezy64b/var/cache/git/mwaite/bin.git atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:310) atorg.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:151) atorg.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:144) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) athudson.remoting.Engine$1$1.run(Engine.java:63) atjava.lang.Thread.run(UnknownSource)Causedby:hudson.plugins.git.GitException:Commandclone--progress-ooriginssh://wheezy64b/var/cache/git/mwaite/bin.gitC:\J\workspace\git-cli-sshreturnedstatuscode128:stdout:CloningintoC:\J\workspace\git-cli-ssh...stderr:error:cannotspawnC:\Users\Alan\AppData\Local\Temp\ssh3783977685963347919.exe:Nosuchfileordirectoryfatal:unabletofork atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:981) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:920) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:64) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:308) ...11moreERROR:nullFinished:FAILURE
{noformat}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Mark Waite closed JENKINS-20356 as Fixed Git CLI cannot clone on Windows using GIT_SSH to set credentials Confirmed closed in git client plugin 1.5.0. Change By: Mark Waite (17/Dec/13 4:26 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Alexander Zeitler edited a comment on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Somehow I managed to get it working using SSH with Jenkins 1.438 and Git Plugin 2.0 and GitLab 6.3: I set the repo url to the SSH url and set it to use no credentials. Using Git bash I removed the passphrase from the key being used (named id_rsa.pub). I also set a username and email for the global Git config. Using GitLab it had to disable "force SSL" (but not disabling this did break my OS X git clone using SSH also). I hope I did not forget anything... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Alexander Zeitler edited a comment on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Somehow I managed to get it working using SSH with Jenkins 1.438 and Git Plugin 2.0 and GitLab: I set the repo url to the SSH url and set it to use no credentials. Using Git bash I removed the passphrase from the key being used (named id_rsa.pub). I also set a username and email for the global Git config. Using GitLab it had to disable "force SSL" (but not disabling this did break my OS X git clone using SSH also). I hope I did not forget anything... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Alexander Zeitler commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials ...and it still works after upgrading to 1.542 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Mark Waite commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials @carolynvs the fix is not in Git plugin 2.0 yet. The fix is in the source code of the git-client-plugin but a version of the client plugin has not been released which includes the fix. Once that fix is released and verified, then the bug report will be "closed". It is expected that it will be fixed in git client plugin 1.4.7. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Alexander Zeitler edited a comment on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Somehow I managed to get it working using SSH with Jenkins 1.438 (on a Windows Server 2012 in Azure) and Git Plugin 2.0 and GitLab 6.3: I set the repo url to the SSH url and set it to use no credentials. Using Git bash I removed the passphrase from the key being used (named id_rsa.pub). I also set a username and email for the global Git config. Using GitLab it had to disable "force SSL" (but not disabling this did break my OS X git clone using SSH also). I hope I did not forget anything... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Alexander Zeitler edited a comment on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Somehow I managed to get it working using SSH with Jenkins 1.438 and Git Plugin 2.0 and GitLab: I set the repo url to the SSH url and set it to use no credentials. Using Git bash I removed the passphrase from the key being used (named id_rsa.pub). I also set a username and email for the global Git config. Using GitLab it had to disable "force SSL" (but this did break my OS X git clone using SSH also). I hope I did not forget anything... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Alexander Zeitler commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Somehow I managed to get it working using SSH with Jenkins 1.438 and Git Plugin 2.0: I set the repo url to the SSH url and set it to use no credentials. Using Git bash I removed the passphrase from the key being used (named id_rsa.pub). I also set a username and email for the global Git config. Using GitLab it had to disable "force SSL" (but this did break my OS X git clone using SSH also). I hope I did not forget anything... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Eric Hartmann commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Just to let you know that the build (1.4.7-SNAPSHOT) of the 1.4.x branch fixes this issue for us. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Mark Waite commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials The only alternatives I've discovered have required that I switch the URL to something other than an ssh URL. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Roland Whitley commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Thanks, unfortunately I have not been very successful with gitlab and http. Commits have usually exceeded size limitations. There were a couple of mentions that this was a recent change. Is there a version that I can roll back to that would bypass this until this fix is released. I only want to consider forking the branch as a final option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Roland Whitley edited a comment on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Thanks, unfortunately I have not been very successful with gitlab and http. Commits have usually exceeded size limitations. Did you mention that this was a recent change and prior releases did not behave like this. Is there a version that I can roll back to that would bypass this until this fix is released. I only want to consider forking the branch as a final option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Mark Waite commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials I believe Git plugin 1.5 worked just fine in this case, as did earlier versions of the plugin, though none of those earlier versions supported the Jenkins credentials store. You'll need to manage the credentials yourself in the job definition, without the convenience of the Jenkins credentials system. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Roland Whitley commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Is there a work around for this issue, or is a code release required in order for this to work. I am getting the same error when trying to connect to a repository in a job configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
