|
||||||||||||||
|
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.
When Jenkins first starts, the value is null because it cannot know the URL.
When Jenkins prepared the system config page, it can add a value to the request field because there's a request coming in from which the value used can be read.
When submitting, the value entered and not changed by the user is recorded so Jenkins knows how to refer to itself (in e.g. emails).
The entire issue is quite complex (e.g. with reverse proxies involved), so it's no wonder the behavior is not that straightforward internally (there are a bunch of different methods to guess the Jenkins URL etc.). From a user POV, the current behavior is probably the best possible; it's just that the configuration should be more prominent. That's a separate issue though.
Since the user behavior is relatively sane and the issue only affects people working with Jenkins internals, resolving as Won't Fix.