When you say "used the private one as my credentials for my user in Jenkins", my initial guess is that you performed an operating system level configuration of the credentials in the user account which runs the Jenkins process. You need to configure the credential in the specific Jenkins job so that the git plugin knows to use that credential for that specific job.
The operating system level configuration should not be needed, now that the git plugin and the git client plugin support credentials. On Sun, May 11, 2014 at 9:02 AM, lesssugar <[email protected]> wrote: > Mark. I generated public/private key pair, saved the public one in my > GitLab, and used the private one as my credentials for my user in Jenkins, > but when I set Repo URL and choose credentials with the private key, I get > this now: > > *Failed to connect to repository : Command "git ls-remote -h > [email protected]:[xxx]/[yyy].git HEAD" returned status code 128:* > *stdout: * > *stderr: Permission denied (publickey). * > *fatal: The remote end hung up unexpectedly* > > When I run ssh -T [email protected] in my console, I see the welcome > message... I'm confused and clearly doing something wrong. But well, I need > to figure it out somehow. Thanks. > > On Sunday, May 11, 2014 4:06:24 PM UTC+2, Mark Waite wrote: >> >> You'll probably have better results if you register that private key as a >> credential (through the "Credentials" page), then use that registered >> credential in your job definition. The git plugin relies on the >> Credentials plugin and uses it so that you can manage credentials through >> the Jenkins web pages. >> >> Mark Waite >> >> >> On Sun, May 11, 2014 at 6:17 AM, lesssugar <[email protected]> wrote: >> >>> Actually, the problem I had was the lack of GIT plugin... I installed it >>> and the wrong URL error is gone. However now when I set GIT repo to my >>> GitLab one, I get this: >>> >>> *Failed to connect to repository : Command "git ls-remote -h >>> [email protected]:[xxx]/[yyy].git HEAD" returned status code 128:* >>> *stdout: * >>> *stderr: Host key verification failed. * >>> *fatal: The remote end hung up unexpectedly* >>> >>> To answer your questons, I don't have any of this set-up, as I really >>> don't know how to do it. I looked for configuration guides for Jenkins + >>> GitLab but none helped me. >>> >>> All I'm trying to achieve is use my GitLab repo in Jenkins, so it can >>> deploy latest changes to my website (remote server). >>> >>> Any help on the subject of setting up the keys and authenticating the >>> connection will be appreciated. >>> >>> On Sunday, May 11, 2014 4:02:38 AM UTC+2, novamine118 wrote: >>>> >>>> what key is jenkins using to authenticate - did you set one up? >>>> >>>> Is jenkin's public key registered with a gitlab user? And does that >>>> gitlab user have access to that repo? The gitlab user also needs to be at >>>> least a "Reporter" (for "pull project code" Action). >>>> >>>> >>>> -Xavier >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Thanks! >> Mark Waite >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
