here is an update the ssh credentials accepted by other types of job are not recognized as ssh credentials in multibranch pipeline...
ERROR: Credentials 'X' is of type 'Username with password' where 'com.cloudbees.jenkins.plugins.sshcredentials.SSHUserPrivateKey' was expected those were created with jcasc if we create credentials manually, in jenkins UI, and they look exactly the same way X does, it works so jcasc creates ssh credentials good enough for some jobs, but multibranch pipeline doesn't recognize it at ssh :( On Thursday, May 23, 2019 at 3:16:45 PM UTC+2, Ewelina Wilkosz wrote: > > I am using exactly the same credentials to clone the same repo in a > different type of job (pipelineJob) at the same agent - so I am almost 100% > sure the credentials and keys are ok. > I am wondering if this is some weird behavior from the plugin that someone > else encountered or maybe I messed something else :) > > On Thursday, May 23, 2019 at 3:11:08 PM UTC+2, Mark Waite wrote: >> >> You might double check that the private key credential you're using with >> that checkout does not use a passphrase, or if it uses a passphrase, does >> not include any shell special characters in the passphrase. There is a >> known bug in the git client plugin handling of ssh passphrases with shell >> special characters. >> >> You might also double check that the private key you're using is >> recognized by both agent and server. I've generated ed25519 private keys >> in the past only to discover that they were not recognized on one or more >> of the old systems that I needed to support. I will be surprised if that >> is the case here, since that usually has a different error message, but it >> is worth checking. >> >> On Thu, May 23, 2019 at 6:57 AM Ewelina Wilkosz <[email protected]> >> wrote: >> >>> I see, >>> >>> but in my case I don't event get to submodules. multibranch pipeline >>> fails on checking out main repo via ssh - I use checkout over SSH option - >>> when a regular pipelineJob has no trouble with ssh >>> >>> On Thursday, May 23, 2019 at 2:44:23 PM UTC+2, Mark Waite wrote: >>>> >>>> Submodule authentication in the git plugin and git client plugin >>>> requires that the same protocol must be used for the parent repository and >>>> the submodules. Different credential methods are required to provide >>>> command line git with http/https credentials than with ssh credentials. A >>>> mix of the two in a single repository definition would require much more >>>> sophisticated operations from the git plugin than it is currently able to >>>> perform. >>>> >>>> If the submodules and the parent repo are all using the same protocol >>>> (ssh or http), then you may need to enable the checkbox which causes the >>>> git plugin to use credentials with submodule operations. I believe it is >>>> disabled by default. >>>> >>>> >>>> On Thu, May 23, 2019 at 5:37 AM Ewelina Wilkosz <[email protected]> >>>> wrote: >>>> >>>>> I have a pipelineJob where I use ssh to clone repository and >>>>> configured credentials, let's call it X, are working great >>>>> >>>>> I also have a multibranch pipeline, where I configured "Checkout over >>>>> SSH" and select same X credentials, but I can't clone >>>>> I get >>>>> >>>>> ERROR: Error fetching remote repo 'origin' >>>>> [...] >>>>> stderr: Permission denied (public key) >>>>> fatal: Could not read from remote repository >>>>> >>>>> The same user could clone via https, but there are some submodules >>>>> configured via ssh, so I need ssh working... >>>>> >>>>> Any ideas? >>>>> >>>>> -- >>>>> 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/89f8e2a2-6082-4642-90ac-31f8da684c06%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/jenkinsci-users/89f8e2a2-6082-4642-90ac-31f8da684c06%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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/a7a0bb7c-4b82-4f7f-b57e-29b9ff210f3e%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-users/a7a0bb7c-4b82-4f7f-b57e-29b9ff210f3e%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/71cc25c6-8bad-4312-a124-b6448162a935%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
