-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Platform: All, OS: All
When configuring a project post-build action with an Ivy file, the Hudson
configure page presents a HTTP 404 error indicating that the
"/publisher/IvyBuildTrigger/checkIvyFile" resource is unavailable. Despite this
message it seems that the module is configured correctly.
[JENKINS-3100] Correctly configured ivy.xml in project post-build action results in HTTP 404 error
jmetcalf
added a comment - Fixed with repository revision 16050. The config.jelly file was erroneously
referring to ${rootUrl} when it should have been referring to ${rootURL}.
Actually I commented out the refactored form validator code since to me it is of
little value. The ivy.xml file is almost never present for a new job since it
is usually managed in the working copy which is generally not checked out yet
for a new job. Therefore the initial configuration will almost always have the
error and this can confuse the new user.
jmetcalf
added a comment - Fixed with repository revision 16050. The config.jelly file was erroneously
referring to ${rootUrl} when it should have been referring to ${rootURL}.
Actually I commented out the refactored form validator code since to me it is of
little value. The ivy.xml file is almost never present for a new job since it
is usually managed in the working copy which is generally not checked out yet
for a new job. Therefore the initial configuration will almost always have the
error and this can confuse the new user. 
Reassigned to myself since I volunteered to fix the issue.