|
||||||||
|
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.
I had considered this type of enhancement but was not sure how to present it in a user interface. Currently, the repository has "Additional Behaviours" which includes the "Advanced clone" section that includes the location of the reference repository. That is a single location for the entire job.
With submodules, the reference repository probably needs to be specified for each submodule as a separate repository, with no promise that there is any pattern between the location of the primary repository and the location of the submodule repositories.
Are you using "reference repository location by convention" for your submodule reference repository definitions, or is there some more sophisticated way to do it that I've not understood?