|
||||||||
|
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/groups/opt_out.
I have a similar experience. We get the following stack trace and failure whenever a build fails. From that point forward, the job shows no available builds or history and any builds will cause the failures seen in JENKINS-17044 (all the executors are dead).
A restart of Jenkins puts everything back to normal, but we lose all the history of the jobs in the sidebar for the job.
I've got two stack traces which I'll attach, plus a screenshot showing no build history. If I restart Jenkins, the build history sort of comes back - but not really. Again, screenshot attached.
I can still access build history for jobs which succeeded via their URL, but jobs that failed get this exception.