|
||||||||
|
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.
Actually, this should probably be a bug.
If someone clicks on a browser link for a revision that exists in the configured repository, they are (incorrectly) shown that changeset.
Since the repo isn't captured in changelog.xml, it's impossible to "know" what repository the change came from.
So...
If multiple repositories are configured
a) Remove the browser from the config and the browser link in the "Changes" section.
b) Set the browser to "None" and if None is set, don't show the browser link in Changes.
c) Fix the problem so the browser can deal with more than one repository.
I'm kind of partial to the third option.