|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-15702) InstantiationE... dave.ehrenber...@solipsys.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... dave.ehrenber...@solipsys.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... dave.ehrenber...@solipsys.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... ho...@farzad.net (JIRA)
- [JIRA] (JENKINS-15702) Instantia... ho...@farzad.net (JIRA)
- [JIRA] (JENKINS-15702) Instantia... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... ho...@farzad.net (JIRA)
- [JIRA] (JENKINS-15702) Instantia... suresh.avadh...@gmail.com (JIRA)
When I restart the error begins reporting when I click on any of my job views. All of them have the condition you said, old job histories. But I don't have to open a particular one. Is there any way to get more details of which job it is complaining about? I do have the option to reinstall and port over the job definitions, but I'd rather not do that.