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

Wed, 11 Feb 2015 02:56:47 -0800

Currently submodules which require SSH credentials do not work in general!

  • If you use the advanced options to update the submodules it will end in a timeout
  • If you put the "git submodule update --init" in a separate cmd task at the job it will also timeout due to it has no credentials.

Only workarround seems so far to make use of the ssh-agent plugin which is complicated on windows due to you will have to install the Apache Tomcat Native libraries on the slave. Alternative is to install he private key on every ssh machine but starting from this point you don't need the credential functionality of the git plugin any more due to the credentials is already available on the slave.

Correct behaviour would to forward the credentials used during clone of the main repository also for all submodule operations.
Having different credentials for main repository and submodules might be an edge case but neither in opensource nor in corporate use.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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.

Reply via email to