[JIRA] (JENKINS-38275) Unable to pull extra repository on build step when running on a Jenkins slave

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title

Mark Waite resolved as Not A Defect   You said: when running a build step (shell script) the slave is losing the GIT_SSH information or that information is not used by git anymore That is the expected behavior. A build step does not have access to the credentials used to clone the repository. Reliably providing credentials to command line git for all credential cases without invoking the command line git program is quite difficult (since there may be a passphrase protected public key, for example), so the plugin does not attempt to share credential information with build steps. If you're using a pipeline job, you can share credential information with pipeline stages using the credentials ID defined in Jenkins. You can refer to the JENKINS-34309 pipeline file in my jenkins-bugs repository for an example pipeline definition that uses a credentials ID. Jenkins / JENKINS-38275 Unable to pull extra repository on build step when running on a Jenkins slave Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect 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.