Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-628

Upgrading from 1.113 to 1.114 loses build history

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • other
    • None
    • Platform: All, OS: All

      Attempts to upgrade from version 1.113 to 1.114 of Hudson loses the project
      history for two of my projects, but one seems to be working. The two projects in
      question use the Trac plugin, but are otherwise the same as the one whose
      project status seems intact. I also tried 1.115 with the same results.

      Downgrading Hudson to 1.113 restores the build history. So I will remain at that
      version until the problem is identified. This saddens me because I really like
      the new storm clouds in the job list.

          [JENKINS-628] Upgrading from 1.113 to 1.114 loses build history

          thorinside created issue -

          Hudson should have left the error message in the container console or the
          container log file. Please get it for me. That is really crucial for me to fix a
          problem like this.

          Kohsuke Kawaguchi added a comment - Hudson should have left the error message in the container console or the container log file. Please get it for me. That is really crucial for me to fix a problem like this.
          Kohsuke Kawaguchi made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          thorinside added a comment -

          Certainly, I will try to get something concrete tomorrow. There were a large
          number of exceptions, many related to parsing of the XML inside the build
          directories. I think, probably, I caused some damage when I disabled the Trac
          plugin and restarted Hudson, that's when I saw a lot of the parsing errors. I
          will copy out all of the logs I can find, then remove them. Then I'll restart
          with 114, and then see if there's any new errors (and if the problem is still
          happening, though I think it will reproduce again).

          thorinside added a comment - Certainly, I will try to get something concrete tomorrow. There were a large number of exceptions, many related to parsing of the XML inside the build directories. I think, probably, I caused some damage when I disabled the Trac plugin and restarted Hudson, that's when I saw a lot of the parsing errors. I will copy out all of the logs I can find, then remove them. Then I'll restart with 114, and then see if there's any new errors (and if the problem is still happening, though I think it will reproduce again).

          thorinside added a comment -

          Created an attachment (id=68)
          Tomcat 5.5 Logs after startup

          thorinside added a comment - Created an attachment (id=68) Tomcat 5.5 Logs after startup

          thorinside added a comment -

          I have attached the logfile from startup of Hudson and hitting the Job list
          page. I am running Tomcat 5.5 with JRE 1.6.0.

          thorinside added a comment - I have attached the logfile from startup of Hudson and hitting the Job list page. I am running Tomcat 5.5 with JRE 1.6.0.

          Just committed a fix towrad 1.116. If you can try a snapshot build to verify the
          fix, that would be great.

          Kohsuke Kawaguchi added a comment - Just committed a fix towrad 1.116. If you can try a snapshot build to verify the fix, that would be great.
          Kohsuke Kawaguchi made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

          thorinside added a comment -

          Okay, I'll do that today. Thanks.

          thorinside added a comment - Okay, I'll do that today. Thanks.

          thorinside added a comment -

          Created an attachment (id=69)
          Tomcat 5.5 Logs after 1.116-SNAPSHOT release tests.

          thorinside added a comment - Created an attachment (id=69) Tomcat 5.5 Logs after 1.116-SNAPSHOT release tests.

            Unassigned Unassigned
            thorinside thorinside
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: