|
||||||||
|
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.
Not sure about #682. It introduces yet another way of creating URLs in Jenkins, adding to a confusing mix (and not helping Jelly pages which still have only ${rootURL}.) It is unnecessary if Jenkins.rootUrl is correctly configured, and inferior to emitting relative links if it is not. (#682 will still produce 404s if you have a reverse proxy which changes the effective context path but have not configured rootUrl.) If it is necessary to handle an unconfigured rootUrl—which is debatable—then we ought to do it right, I think.