I faced the same issue and I decided to recompile the git plugin (actually 
the git-client plugin which is a dependency of the git plugin) with the 
patch submited in that Pull Request: 
https://github.com/jenkinsci/git-client-plugin/pull/180/files (Note I'm not 
the author of this patch)

It handles the single sub-case where all git submodules are using the same 
credentials (and this is probably why it has not been merged yet) but it 
works for me.

-- 
JC

Le lundi 24 août 2015 21:45:38 UTC+2, Pratik Dhandharia a écrit :
>
> Hi All,
>
> I am comparatively new to Jenkins and I am trying to troubleshoot a 
> Jenkins issue where we are trying to fetch a public repository which has 
> multiple private sub-modules. It is due to legal reasons we cannot keep the 
> private sub-modules public.
>
> So I have most of the plugin's installed in Jenkins. I have configured 
> Jenkins to store the jenkins user credential using the credential plugin. 
>
> What I am really trying to do is, fetching the private sub-modules using 
> credentials (username and password). I don't want to switch to using SSH 
> key of the jenkins user for pulling the private sub-modules. And here is 
> the error that I get:
>
>  > /usr/bin/git submodule sync # timeout=10
>  > /usr/bin/git config --get remote.origin.url # timeout=10
>  > /usr/bin/git submodule update --init --recursive
> FATAL: Command "/usr/bin/git submodule update --init --recursive" returned 
> status code 1:
> stdout: 
> stderr: fatal: Authentication failed
> Unable to fetch in submodule path
>
>
> Can someone please help point out if the Jenkins Git Client Plugin, work 
> with fetching private repositories using credentials(username and password)?
>
> Thanks
>

-- 
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/6d414fb4-ddc5-443c-bda5-d34dfa08d5cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to