I'll improve the docs. I also want to look into why authentication over HTTPS is not supported. That is a painful bug now that we set up authentication for new instances more aggressively for obvious reasons...
On Tue, Jun 28, 2016 at 11:45 PM Sverre Moe <[email protected]> wrote: > Yes, that worked. Thanks. > > > onsdag 29. juni 2016 00.14.07 UTC+2 skrev Kohsuke Kawaguchi følgende: > >> You should use your user name on Jenkins. You'll also need to register >> your public key on Jenkins. See http://LOCATION/me/configure >> >> On Tue, Jun 28, 2016 at 3:27 AM Sverre Moe <[email protected]> wrote: >> > >>> - ssh://USERNAME@server:PORT/workflowLibs.git through Jenkins SSH >>> <https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+SSH> >>> - http://LOCATION/workflowLibs.git (when your Jenkins app is located >>> on the url http://LOCATION/). As noted in JENKINS-26537 >>> <https://issues.jenkins-ci.org/browse/JENKINS-26537>, this mode will >>> not currently work in an authenticated Jenkins instance. >>> >>> Since the jenkins server is authenticated and using https I have to use >>> ssh:// to clone the workflowLibs.git repository. >>> I have configured jenkins with SSHD and enabled it on port number xxxxx. >>> I am not sure which USERNAME to use. >>> >>> I tried setting a password for the jenkins user, but it wouldn't work >>> cloning workflowLibs.git with that user. >>> git clone ssh://[email protected]:xxxxx/workflowLibs.git >>> >>> Cloning into 'workflowLibs'... >>> Permission denied (publickey). >>> fatal: Could not read from remote repository. >>> >>> Please make sure you have the correct access rights >>> and the repository exists. >>> >>> For now I have initialized the repository directly on the >>> server:/var/lib/jenkins/workflow-libs and manually transferred the files >>> over. It is not a method I would rely on, but it work for now to get my >>> build scripts in CPS global lib. >>> >>> -- >>> 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 [email protected]. >> >> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/534e6cde-aaa0-4d58-9279-7d89d4dccd57%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/534e6cde-aaa0-4d58-9279-7d89d4dccd57%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/ea92e133-a87e-4ffb-acf7-51286d143edd%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/ea92e133-a87e-4ffb-acf7-51286d143edd%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAN4CQ4xcqPz5edDgV4mX0V8LtpmHXjwbdT-JuHZBrTG7SVqKvg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
