[JIRA] (JENKINS-15333) Unable to see build history after upgrade
Kohsuke Kawaguchi resolved JENKINS-15333 as Incomplete Unable to see build history after upgrade There have been several fall out issues that stem from JENKINS-8754 (see the issues linked from that), and some critical fixes such as JENKINS-15587 is just getting into 1.507. This ticket is clearly related to this, but it just doesn't have enough details for us to act on. Because many of those issues have been fixed since this issue has been reported, I'm marking this closed as INCOMPLETE. If you continue to see problems post 1.507, please open separate tickets and include the stack trace from the server console output, as well as your OS and whether the symlink support is enabled. Change By: Kohsuke Kawaguchi (13/Mar/13 10:33 PM) Status: Open Resolved Assignee: KohsukeKawaguchi Resolution: Incomplete 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.
[JIRA] (JENKINS-15333) Unable to see build history after upgrade
josh kehoe commented on JENKINS-15333 Unable to see build history after upgrade This is happening to us too, but randomly. A restart of Jenkins restores the history but after a few days, it disappears again. This started happening after upgrading to 1.485. 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-15333) Unable to see build history after upgrade
Richard Mortimer commented on JENKINS-15333 Unable to see build history after upgrade @josh kehoe I suspect that your problen is different to the earlier reported problem. Yours sounds more like JENKINS-15465 and that is fixed in 1.486 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-15333) Unable to see build history after upgrade
Richard Mortimer commented on JENKINS-15333 Unable to see build history after upgrade For those who are seeing problems in 1.483 can you check the jenkins.log file to see if any errors are reported there. It is likely that something changed in either Jenkins core or a plugin that stopped older builds from being read from disk. The log contents should help diagnose that. 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-15333) Unable to see build history after upgrade
josh kehoe commented on JENKINS-15333 Unable to see build history after upgrade Thank you, I'll give that a try. For some reason though, my instance of Jenkins thinks it's on the latest release and is not seeing 1.486 as being available yet. I'll have to update manually. 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-15333) Unable to see build history after upgrade
wbauer commented on JENKINS-15333 Unable to see build history after upgrade Same problem here when upgrading from 1.480 to 1.483 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-15333) Unable to see build history after upgrade
Ian Rogers created JENKINS-15333 Unable to see build history after upgrade Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 27/Sep/12 11:16 AM Description: Upgraded from 1.474 to 1.483 and am now unable to see old build history. New builds are creating history that can be viewed. Old builds exist on the filesystem, but no build.xml within build subdirectory. New builds also exist, with build.xml. Environment: RedHat Linux 5.6 x86_64 Tomcat 6.0.32 Java 1.6.0_24 64-bit Project: Jenkins Priority: Major Reporter: Ian Rogers 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
