Re: Problem when trying to connect to GitHub from a Windows slave
Hello David, Many thanks for your response! eyal david (2019/05/27 18:37 +0300): > Hi > Try to recreate new keys from the windows slave using the git bash ... What do you mean by git bash ? > than create credentails id in jenkins master based on the your private key > created on the windows slave And hten of course the public key needs to be added on GitHub. Well since the manual clone worked I'm a bit reluctant to do all this, I have to say. Sébastien. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20190527204254.GA2102%40prajna.paris.inria.fr. For more options, visit https://groups.google.com/d/optout.
Re: Problem when trying to connect to GitHub from a Windows slave
Hi, Many thanks for your response. Geoffroy J (2019/05/27 09:18 -0700): > Hello > > Have you tried cloning manually using the ssh key on windows? Yes, and it worked. Sorry I forgot to mention this. > Also, what username have you configured for your git credential on > Jenkins? The GitHub user name. But the 'git@' part in the URL of the repository. Additionnally, as I mentionned, this setting works perfectly well for the Unix machines. > I faced ssh issues on windows because of change in SSH/GIT and it was > necessary to set credential username to 'git' instead of the real github > username. See https://issues.jenkins-ci.org/browse/JENKINS-50573 Thanks! Actually, my GitHub plugin is up-to-date so I'd expect this to be fixed, right? Also my error message is different from the one reported in the bug, mine explicitly mentions an "invalid format" in the keyfile. But many thanks for helping out, I really appreciate and hope we willl find the problem! Sébastien. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20190527203246.GB1939%40prajna.paris.inria.fr. For more options, visit https://groups.google.com/d/optout.
Re: Problem when trying to connect to GitHub from a Windows slave
Hello Have you tried cloning manually using the ssh key on windows? Also, what username have you configured for your git credential on Jenkins? I faced ssh issues on windows because of change in SSH/GIT and it was necessary to set credential username to 'git' instead of the real github username. See https://issues.jenkins-ci.org/browse/JENKINS-50573 BR On Monday, 27 May 2019 16:50:59 UTC+2, Sébastien Hinderer wrote: > > Dear all, > > Recently, I wanted my slaves to fetch our GitHub repository through > authenticated ssh coneections rather than through HTTPS unauthenticated > connections. > > I created the appropriate Jenkins credential with ssh keys, replaced the > HTTPS URL of the repo by an ssh-based one and requested the use of the > newly created credential. > > On our Unix machines everything works like a charm. > > On our Windows machines, though, I get an "invalid format" message while > trying to read a .key file. > > In case it's useful, our Windows hosts are running git 2.17.0 and > OpenSSH 7.8p1. > > Many thanks in advance for any hint! > > Sébastien. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ddb9de8e-9a6d-4c3a-892d-4a08c9501322%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Problem when trying to connect to GitHub from a Windows slave
Dear all, Recently, I wanted my slaves to fetch our GitHub repository through authenticated ssh coneections rather than through HTTPS unauthenticated connections. I created the appropriate Jenkins credential with ssh keys, replaced the HTTPS URL of the repo by an ssh-based one and requested the use of the newly created credential. On our Unix machines everything works like a charm. On our Windows machines, though, I get an "invalid format" message while trying to read a .key file. In case it's useful, our Windows hosts are running git 2.17.0 and OpenSSH 7.8p1. Many thanks in advance for any hint! Sébastien. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20190527135323.GA32420%40prajna.paris.inria.fr. For more options, visit https://groups.google.com/d/optout.
