My docker image is doing fine, but the standalone Jenkins just won't authenticate with either JGit or git. It would be really nice to be able to do this without docker. Is there a standard launch recipe for my situation (in Ubuntu) or is SSH with passphrases just not available anymore?
java -jar jenkins.war doesn't cut it. :( On Wednesday, April 24, 2019 at 3:14:49 PM UTC-4, Randall Becker wrote: > > I'm rebuilding both docker and standalone images and will compare. The > docker image is fine with the key pair after I restarted it. I also had to > pick off the host signature using ssh -i blah g...@bitbucket.org... THEN the > docker image was able to authenticate. I'm going to try the same on the > standalone. > > On Wednesday, April 24, 2019 at 2:57:59 PM UTC-4, Mark Waite wrote: >> >> I've been using 2.164.1 and 2.164.2 since their release with both Java 8 >> and Java 11, alternating between various configurations, I'm confident the >> update is not DOA. >> >> I use bitbucket repositories that are secured with passphrase protected >> private keys. I use GitHub repositories that are secured with passphrase >> protected private keys. Check your configuration carefully. Has the >> passphrase protected private key been disabled in bitbucket? Is Jenkins >> reporting any issue with the private key format? >> >> On Wed, Apr 24, 2019 at 12:53 PM Randall Becker <the....@gmail.com> >> wrote: >> >>> I went back to try to use 2.164 on Docker and am experiencing similar >>> issues. I wonder whether this update is DOA. >>> >>> On Wednesday, April 24, 2019 at 2:45:16 PM UTC-4, Mark Waite wrote: >>>> >>>> >>>> >>>> On Wed, Apr 24, 2019 at 12:35 PM Randall Becker <the....@gmail.com> >>>> wrote: >>>> >>>>> I should qualify... the passphrase prompt disappeared when setsid is >>>>> used, but that still does not allow a passphrase-less keypair. >>>>> >>>>> >>>> That may indicate that you have another problem. If the passphrase >>>> prompt disappeared, then ssh should have either completed the ssh >>>> authentication or reported an error message. >>>> >>>> >>>>> On Wednesday, April 24, 2019 at 2:33:07 PM UTC-4, Randall Becker wrote: >>>>>> >>>>>> The Multibranch Pipeline Plugin using JGit ends up incompatible. >>>>>> >>>>>> > /usr/local/bin/jgit --version # timeout=10 >>>>>> > /usr/local/bin/jgit ls-remote --symref >>>>>> g...@bitbucket.org:nonstop-git/nsgit.git # timeout=10 >>>>>> >>>>>> ERROR: [Wed Apr 24 18:23:01 UTC 2019] Could not update folder level >>>>>> actions from source 0819144a... >>>>>> hudson.plugins.git.GitException: Command "/usr/local/bin/jgit ls-remote >>>>>> --symref g...@bitbucket.org:group/repo.git" returned status code 1: >>>>>> stdout: >>>>>> stderr: fatal: "--symref" is not a valid option >>>>>> >>>>>> Looks like JGit (5.3.0 anyway) is no longer an option for polling. >>>>>> I'm on Git Plugin 3.9.3. >>>>>> >>>>>> setsid made no difference. >>>>>> >>>>>> On Wednesday, April 24, 2019 at 2:24:00 PM UTC-4, Mark Waite wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Apr 24, 2019 at 12:10 PM Randall Becker wrote: >>>>>>> >>>>>>>> I'll bite. How can I use JGit instead of git in Jenkins? I thought >>>>>>>> it was hard-burnt into the Git Plugin. >>>>>>>> >>>>>>>> >>>>>>> In the "Global Tools Configuration" page of "Manage Jenkins", use >>>>>>> the "Git" button and the "Add" button under it to add "jgit" as an >>>>>>> implementation. Once you've done that, then jobs will have an >>>>>>> additional >>>>>>> option to select which git implementation they will use. >>>>>>> >>>>>>> >>>>>>>> On Wednesday, April 24, 2019 at 1:08:48 PM UTC-4, Randall Becker >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> This is a new situation that I have encountered after a clean >>>>>>>>> install of 2.164. Attempting to use an SSH keypair (with passphrase) >>>>>>>>> to >>>>>>>>> talk to BitBucket.org, in a Multibranch Pipeline job. The key is >>>>>>>>> properly >>>>>>>>> configured as an Private Key (entered manually) with a Passphrase. >>>>>>>>> >>>>>>>>> When I hit Scan Multibranch Pipeline Now, Jenkins immediately >>>>>>>>> prompts the JVM's stderr for the passphrase. As an example: >>>>>>>>> >>>>>>>>> Enter passphrase for key '/tmp/ssh6766884284790436436.key': >>>>>>>>> >>>>>>>>> I also get an error in the Multibranch scan log: >>>>>>>>> >>>>>>>>> > git ls-remote g...@bitbucket.org:group/repo.git # edited, of course >>>>>>>>> ERROR: [Wed Apr 24 16:58:41 UTC 2019] Could not update folder level >>>>>>>>> actions from source 73a4292e-,,,, >>>>>>>>> hudson.plugins.git.GitException: Command "git ls-remote >>>>>>>>> g...@bitbucket.org:group/repo.git" returned status code 128: >>>>>>>>> stdout: >>>>>>>>> stderr: Permission denied (publickey). >>>>>>>>> fatal: Could not read from remote repository. >>>>>>>>> >>>>>>>>> >>>>>>>>> This is bizarre. I'm running Ubuntu 16.04 using the default JRE. >>>>>>>>> This did not happen on earlier versions of Jenkins that were running >>>>>>>>> in >>>>>>>>> Docker images - I had to remove Docker for VPN reasons. >>>>>>>>> >>>>>>>>> I'm basically off the air at this point. Did I just miss a plugin >>>>>>>>> or do something silly? >>>>>>>>> >>>>>>>>> TIA, >>>>>>>>> Randall >>>>>>>>> >>>>>>>> -- >>>>>>>> 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 jenkins...@googlegroups.com. >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/30f56e57-d3de-4e43-96dc-d07aa4ebdcda%40googlegroups.com >>>>>>>> >>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/30f56e57-d3de-4e43-96dc-d07aa4ebdcda%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> 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 Users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to jenkins...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-users/69755a15-a748-49e6-bb95-a9347afa75cc%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/jenkinsci-users/69755a15-a748-49e6-bb95-a9347afa75cc%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> 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 Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to jenkins...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/d54ac82a-1a1d-4b40-968a-d2357addac6d%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-users/d54ac82a-1a1d-4b40-968a-d2357addac6d%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> 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 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/c4fc1bf8-31ec-4b3c-a1e7-3ae00994a047%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
