|
|
|
Issue Type:
|
Improvement
|
Assignee:
|
Unassigned |
Components:
|
core |
Created:
|
22/Jul/14 5:45 AM
|
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.
|
Environment:
|
Jenkins 1.574-SNAPSHOT
|
Project:
|
Jenkins
|
Labels:
|
job
corruption
usability
|
Priority:
|
Minor
|
Reporter:
|
Craig Ringer
|
|
|
|
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
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.