|
||||||||
|
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-15587) Builds disappear f... [email protected] (JIRA)
- [JIRA] (JENKINS-15587) Builds disapp... [email protected] (JIRA)
- [JIRA] (JENKINS-15587) Builds disapp... [email protected] (JIRA)
- [JIRA] (JENKINS-15587) Builds disapp... [email protected] (JIRA)
- [JIRA] (JENKINS-15587) Builds disapp... [email protected] (JIRA)
- [JIRA] (JENKINS-15587) Builds disapp... [email protected] (JIRA)
- [JIRA] (JENKINS-15587) Builds disapp... [email protected] (JIRA)
- [JIRA] (JENKINS-15587) Builds disapp... [email protected] (JIRA)
- [JIRA] (JENKINS-15587) Builds disapp... [email protected] (JIRA)
- [JIRA] (JENKINS-15587) Builds disapp... [email protected] (JIRA)
- [JIRA] (JENKINS-15587) Builds disapp... [email protected] (JIRA)

Have you recently tried running Jenkins under Java 7 and then switched back to Java 6 or less? I experienced this issue where after a trial period under Java 7, switching back caused the build number shortcut folders to cause this exception.
I managed to workaround this by just removing the shortcut folders which didnt impact the load up of the jobs.