|
||||||||
|
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.
Yeah, this issue is a real pain for us too.
The only way we could get it working for our Stash/Jenkins setup was to create a read-only user and to hard code this user's credentials in the reference to the submodule.
Although bad practise, all users working on the git repo already have at least read-only access, so we didn't feel it was too much of a security concern.
e.g. in the parent repo .gitmodules file:
[submodule "shared-library"] path = shared-library url = "" class="code-comment">//username:passw...@stash.yourcompany.com/scm/project/shared-library.git