Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353811 - Error message stating missing Hudson URL may be misleading.
Summary: Error message stating missing Hudson URL may be misleading.
Status: RESOLVED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Torkild Resheim CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-03 14:57 EDT by Torkild Resheim CLA
Modified: 2011-08-04 06:55 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Torkild Resheim CLA 2011-08-03 14:57:15 EDT
It appears that the error message stating "Hudson server running at {0} cannot be added as no URL has been specified in the Hudson control panel." may be misleading. This error message will in some circumstances be shown even if an URL has been specified.

This needs further investigation and must be resolved.
Comment 1 Torkild Resheim CLA 2011-08-04 05:29:24 EDT
At least for Jenkins 1.424 it appears that it is impossible to set the server URL to an empty value. It will be replaced with the default "http://localhost:8080/". However the URL is sometimes missing from the UDP broadcast message and looking at the Jenkins code this happens when the server URL is NULL. See https://github.com/jenkinsci/jenkins/blob/f28409ee272fdb989d28083aa19dfb29e9fda2b2/core/src/main/java/hudson/DNSMultiCast.java.

I've tried changing the URL and restarting Jenkins several times and I cannot find a pattern. It seems that the "url" property randomly drops out.
Comment 2 Torkild Resheim CLA 2011-08-04 06:55:44 EDT
Testing with Hudson reveals that it does not exhibit the behaviour described in comment #1. On the contrary it always announces itself properly when started (unlike Jenkins). Closing as WONTFIX as this appears to be a Jenkins only issue.