You mentioned that the https clone works "provided, I have my public keys in place". Then later you mentioned that you want it to work without requiring a public key. I think the problem is with your server configuration, rather than with Jenkins. If I'm right, there are several ways you could change your server configuration.
You might consider using git protocol rather than https protocol, since it performs no authentication and no SSL encryption. If you can't configure to use the git protocol rather than https, then you should probably test a clone from an account which does not have your public keys in place. That will allow you to see what Jenkins sees, and perform experiments until the https server configuration does not require public keys be in place. Another alternative is to use the Jenkins Credentials feature to add your private key to the Jenkins instance so that the keys are available to the Jenkins process the same as they are available to your user process. Thanks, Mark Waite On Thu, Oct 31, 2013 at 2:44 PM, <slouie.at.w...@gmail.com> wrote: > Thanks for the reply. Yeah, I don't want to use ssh. I want to use > https. > > > On Thursday, October 31, 2013 1:24:40 PM UTC-7, Maneesh M P wrote: >> >> if you want to use git clone over ssh, keep your key at >> /var/lib/jenkins/.ssh then git clone will work just like how it works in >> your command line. >> >> Thanks, >> Maneesh >> >> On Thursday, October 31, 2013 1:15:12 PM UTC-7, slouie....@gmail.comwrote: >>> >>> If I can add, in my initial post, I was running Jenkins as a service >>> account user (we'll call jenkins). >>> >>> I also installed a local Jenkins just to debug. If I ran Jenkins as >>> myself and for the repository URL, i typed ssh://first.l...@blah.com:** >>> 8443/blah.git <http://first.l...@blah.com:8443/blah.git>, this worked >>> fine so I'm not sure what's wrong with my git or Jenkins config. Running >>> git frmo command line works for both ssh and https. Jenkins works for ssh >>> when Jenkins is run as myself. Jenkins doesn't work on ssh and https when >>> it's not run by me. >>> >>> >>> On Thursday, October 31, 2013 1:07:37 PM UTC-7, slouie....@gmail.comwrote: >>>> >>>> Hi, >>>> >>>> I'm a noob to Jenkins so please forgive me if this is a dumb question. >>>> I'm trying to use Jenkins to pull down our code from git to make a build. >>>> Someone told me to use anonymous read-only access via https in Jenkins >>>> so we can pull down our code w/o public keys or what not. >>>> In my project, I click on "Configure". Under Source Code >>>> Management>Git>Repository URL, I type in our repo url. >>>> >>>> https://blah.com:8443/blah.git >>>> >>>> Jenkins returns this message below. >>>> Failed to connect to repository : Failed to connect to >>>> https://blah.com:8443/blah.git >>>> >>>> The funny thing is when I'm on the command line, I can type this and >>>> git works fine: >>>> >>>> git clone https://blah.com:8443/blah.git >>>> >>>> I also tried this on the cmd line too, which also worked, provided, I >>>> have my public keys in place. >>>> git clone >>>> ssh://first.l...@blah.com:**8443/blah.git<http://first.l...@blah.com:8443/blah.git> >>>> >>>> What do I need to do in Jenkins so that it pulls my code down w/o >>>> problems, just like the command line examples? Do I need to do something >>>> on the git repo to get this to work with Jenkins? >>>> >>>> Thanks in advance for your help. >>>> >>> -- > 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. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
