Details
-
Type:
New Feature
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: core
-
Labels:
-
Environment:Jenkins 1.574-SNAPSHOT
-
Similar Issues:
Description
As part of JENKINS-23914 I noticed that jobs that Jenkins fails to load completely vanish from the UI. They're still present in jobs/jobname/config.xml, but the only indication they exist in the UI is an error in the log where they failed to load.
It would be a usability improvement helpful if, in cases where the job XML was parsed successfully but the job objects couldn't be created, jenkins displayed a "broken" job in the job-list which shows the exception encountered when loading the job when opened.
Vanishing jobs aren't fun, especially if you don't know how to fix them by hand.
Attachments
Activity
Good point. In the mean time, hopefully people searching for "jenkins job vanished" will find this and know to look in the jenkins error log.
Craig Ringer
added a comment - Good point. In the mean time, hopefully people searching for "jenkins job vanished" will find this and know to look in the jenkins error log. Did you check Manage Jenkins, or Manage Jenkins » Manage Old Data to see whether this exists already? Most loading errors should already appear at least in Old Data...
I looked in there when getting the exception above from the logs. I don't recall the red-highlighted message about old/unreadable data appearing then. If I get the chance to restart the node I'll try intentionally breaking a build XML and seeing if it shows up.
Craig Ringer
added a comment - I looked in there when getting the exception above from the logs. I don't recall the red-highlighted message about old/unreadable data appearing then. If I get the chance to restart the node I'll try intentionally breaking a build XML and seeing if it shows up. 
An administrative monitor (the messages on the top of "Manage Jenkins") pointing out unloadable data would probably be a better solution. Creating "proxy" items in the hierarchy would on one hand make permissions handling difficult (should everyone with read permission to the real thing have read permissions to the error message item?), and wouldn't be visible enough on large instances.