• Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major Major
    • core
    • RedHat Linux 5.6 x86_64
      Tomcat 6.0.32
      Java 1.6.0_24 64-bit

      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.

          [JENKINS-15333] Unable to see build history after upgrade

          wbauer added a comment -

          Same problem here when upgrading from 1.480 to 1.483

          wbauer added a comment - Same problem here when upgrading from 1.480 to 1.483

          josh kehoe added a comment -

          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.

          josh kehoe added a comment - 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.

          @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

          Richard Mortimer added a comment - @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

          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.

          Richard Mortimer added a comment - 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.

          josh kehoe added a comment -

          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.

          josh kehoe added a comment - 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.

          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.

          Kohsuke Kawaguchi added a comment - 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.

            kohsuke Kohsuke Kawaguchi
            irogers Ian Rogers
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: