[JIRA] [git-client-plugin] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service

2016-03-19 Thread tayneshei...@msn.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Taylor Nesheim commented on  JENKINS-20356 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service  
 
 
 
 
 
 
 
 
 
 
Ryan Pavlik: Hey Ryan, so I was having the same issue you were having regarding https://issues.jenkins-ci.org/browse/JENKINS-20941. So it turns out that Jenkins uses the systemprofile as its default user when it runs. So in order to get this to work I needed to copy my .ssh into the home directory of the systemprofile which for me resides at C:\Windows\system32\config\systemprofile. But for your specific machine you can run the echo %USERPROFILE$ cmd in a Jenkins job to confirm what that directory is.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service

2016-02-09 Thread r...@sensics.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Pavlik commented on  JENKINS-20356 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service  
 
 
 
 
 
 
 
 
 
 
I may be experiencing this in what I reported in https://issues.jenkins-ci.org/browse/JENKINS-20941?focusedCommentId=247772=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-247772 
There, I have a private github repo, with SSH credentials set, specified as g...@github.com:sensics/abcde.git , which I think cloned fine on its own. It has submodules specified, in the same format, for which the same credential should work, in the repo, and the additional submodule behaviors added to the config, but the "access rights" error as seen above occurs for the submodules. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service

2015-09-20 Thread horn.d...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Drew Horn commented on  JENKINS-20356 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service  
 
 
 
 
 
 
 
 
 
 
I'm seeing the same issue where the clone fails due to permissions even when the proper SSH key is set for the project. The same project buliding on os x or linux works fine. I think GIT_SSH can't set the ssh key properly before trying to clone on the windows box: 

 
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Command "C:\Program Files\Git\cmd\git -c core.askpass=true fetch --tags --progress g...@github.com: +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
 

 
Versions: 
Git version: 2.5.3 Jenkins 1.6.129 Git Plugin 2.4.0 Windows 10 (build-agent – agent installed as windows service) 
I'll follow up if I find a workaround. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service

2015-09-20 Thread horn.d...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Drew Horn edited a comment on  JENKINS-20356 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service  
 
 
 
 
 
 
 
 
 
 I'm seeing the same issue where the clone fails due to permissions even when the proper SSH key is set for the project. The *same* project buliding on os x or linux works fine. I think GIT_SSH can't set the ssh key properly before trying to clone on the windows box:{noformat}ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "C:\Program Files\Git\cmd\git -c core.askpass=true fetch --tags --progress g...@github.com: +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists.{noformat}Versions:Git version: 2.5.3Jenkins 1.6.129Git Plugin 2.4.0Windows 10 (build-agent -- agent installed as windows service)I'll follow up if I find a workaround.**UPDATE** - I had to work around this by just deleting the SSH Credential in Jenkins and just setting a public/private key  for  on  the windows  box to use  slave itself  (in ~/.ssh)  which will be used  for all builds. Not ideal as using different SSH keys for building different projects in different git repos is ideal. Perhaps an environment variable isn't being set before trying to run git? Unsure. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service

2015-09-20 Thread horn.d...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Drew Horn edited a comment on  JENKINS-20356 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service  
 
 
 
 
 
 
 
 
 
 I'm seeing the same issue where the clone fails due to permissions even when the proper SSH key is set for the project. The *same* project buliding on os x or linux works fine. I think GIT_SSH can't set the ssh key properly before trying to clone on the windows box:{noformat}ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "C:\Program Files\Git\cmd\git -c core.askpass=true fetch --tags --progress g...@github.com: +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists.{noformat}Versions:Git version: 2.5.3Jenkins 1.6.129Git Plugin 2.4.0Windows 10 (build-agent -- agent installed as windows service)I'll follow up if I find a workaround. **UPDATE** - I had to work around this by just deleting the SSH Credential in Jenkins and just setting a public/private key for the windows box to use (in ~/.ssh) for all builds. Not ideal as using different SSH keys for building different projects in different git repos is ideal. Perhaps an environment variable isn't being set before trying to run git? Unsure. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service

2015-05-21 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-20356 
 
 
 
  Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Assignee:
 
 MarkWaite 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service

2014-12-25 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 assigned  JENKINS-20356 to Unassigned



Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service
















Change By:


Mark Waite
(26/Dec/14 5:16 AM)




Assignee:


NicolasDeLoof



























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-client-plugin] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service

2014-12-25 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 assigned  JENKINS-20356 to Mark Waite



Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service
















Change By:


Mark Waite
(26/Dec/14 5:17 AM)




Assignee:


MarkWaite



























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.