|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
I think that is an interesting performance optimization. I think you're proposing that the plugin could apply the same logic as the "git clone" command. If the path to the repository is a local path (e.g. "/x/y/z" or "../x/y/z"), then we could infer the --local option just as "git clone" does.
I assume there are not many Jenkins users dependent on that local optimization, so there won't be many people who would benefit from that optimization.