|
||||||||
|
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/groups/opt_out.
I'm of the opposite opinion. I think the "--local" option is unintuitive in a Jenkins context, since it seems it will only work if the repository URL is a path to a repository on the same file system as the Jenkins workspace. I rarely have a Jenkins environment with no slaves, and when I add the slaves, that "same file system" requirement is no longer a workable requirement.
The reference option allows me to use the same configuration on the job whether it executes on the master or the slave, and I get the benefit of the reference repository if the referenced bare repository is available.