Jenkins URL field is showing a value even not being set (it is actually unset in config.xml). This behaviour is confusing for users (it seems to be set, but it's not).
One things to improve it:
Don't set the value in the field, but suggest it (form validation)- Add an administrative monitor pointing to it
- causes
-
JENKINS-60750 Setup wizard asks to set root URL even when already set if admin user creation skipped
-
- Resolved
-
- is blocked by
-
JENKINS-51660 Setup wizard suggests root URL not ending in slash
-
- Resolved
-
-
JENKINS-51816 'Instance Configuration' step displays request result
-
- Resolved
-
- is blocking
-
JENKINS-33508 Don't offer Bitbucket Team Source Repo webhook configuration while Jenkins URL is unconfigured
-
- Resolved
-
- is duplicated by
-
JENKINS-28466 Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked
-
- Closed
-
- is related to
-
JENKINS-32192 Hyperlinks quietly fail when JenkinsLocationConfiguration incorrect
-
- Open
-
- relates to
-
JENKINS-51064 Lenient URL validator for Root URL
-
- Resolved
-
-
JENKINS-47426 ClientAuthenticationCache#getPropertyKey not consistent when rootUrl is not set
-
- Resolved
-
- links to
Since this has been merged in 2.119, my Jenkins installation is constantly showing the "Jenkins root URL seems to be invalid. It is required for the proper operation of many Jenkins features like email notifications, PR status update, and environment variables such as BUILD_URL." notification.
I have tried modified the URL setting to a completely different value, and then back to the correct value to ensure that it is definitely set, yet this message continues to display (even after a Jenkins restart).
The configured URL is definitely correct. I'm guessing there's some extra check being performed which makes Jenkins believe it to be incorrect - most likely something related to the docker / nginx setup I've got going on. However, I feel like there should be a simple way of confirming to Jenkins that yes, the URL as configured is the correct one for it to be using and to stop prompting about it.