[JIRA] (JENKINS-20941) Stored git credentials not used when submodule is updated

[yury.zayt...@traveltainment.de (JIRA)]

Title: Message Title

Yury Zaytsev commented on JENKINS-20941   Re: Stored git credentials not used when submodule is updated FYI, very sadly, the ability to select advanced git behaviors in multibranch pipeline projects is gone again after upgrade from 2.5.2 to 3.0.0-beta1 of the git plugin. I was assuming 3.0.0-beta1 is necessary to go with 2.0.0-beta1 of the git client plugin. After I downgraded to git plugin 2.5.2 again, but left git client 2.0.0-beta1 in, submodule (public key) authentication on the agents still doesn't seem to work even though the main repository is checked out just fine > git submodule update --init --recursive XXX hudson.plugins.git.GitException: Command "git submodule update --init --recursive XXX" returned status code 128: stdout: stderr: Cloning into 'XXX'... Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,password). fatal: Could not read from remote repository. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.