|
||||||||
|
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.
Another common case would be the links in the build failure notifications. No HTTP request anywhere.
Note that supporting different Jenkins URLs opens a whole can of worms, e.g. wrt cookies. You click a link sent by a colleague (who prefers the IP address he's always used over the nice server name) and you go WHY AM I NOT LOGGED IN? THIS IS BULL****!
Of course, the same issue occurs today, but I expect that with the alias feature comes an expectation that things like this "just work".