|
||||||||
|
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.
Hi Nicolas,
do I understand that "fix" right: instead of providing an alias you use the URI directly, so no specified alias is set?
If so, we might get problems with functionality that relies on a given remote alias. For example the "git publish" plugin uses a remote alias to push specific branches to.
In that case, wouldn't it better to ensure, the given specification was set as remote alias. I currently see the method GitClient:setRemoteUrl() that could help. But I'm not really sure, as I do not get the whole architecture yet.