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

Build records not migrated due to “failed to rename” on Windows

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • None
    • 1.597 on Windows

      After updating from 1.596 to 1.597 I seem to have wrong "last success" timestamps. See attached images.

        1. 2014-11-26_03-40-28 build.xml
          5 kB
        2. tag-builds-dir.txt
          1 kB
        3. builds directory.jpg
          builds directory.jpg
          170 kB
        4. Error Log SH - 3953 .txt
          902 kB
        5. jenkins.err.log_on-startup.txt
          119 kB
        6. job-builds.dir.txt
          0.8 kB
        7. job.dir.txt
          0.8 kB
        8. build.png
          build.png
          6 kB
        9. lastSuccess.png
          lastSuccess.png
          6 kB

          [JENKINS-26519] Build records not migrated due to “failed to rename” on Windows

          Heiko Tappe created issue -

          Daniel Beck added a comment -

          When you select a job, are the dates in the build history widget correct? Is the date correct when viewing a single build?

          Daniel Beck added a comment - When you select a job, are the dates in the build history widget correct? Is the date correct when viewing a single build?

          Heiko Tappe added a comment -

          Old builds' dates are incorrect (01.01.1970), new builds (after having updated to 1.597) are correct. Same for viewing a single build.

          Heiko Tappe added a comment - Old builds' dates are incorrect (01.01.1970), new builds (after having updated to 1.597) are correct. Same for viewing a single build.

          Daniel Beck added a comment -

          This seems pretty bad. Assigning to jglick speculatively.

          Daniel Beck added a comment - This seems pretty bad. Assigning to jglick speculatively.
          Daniel Beck made changes -
          Assignee New: Jesse Glick [ jglick ]
          Priority Original: Minor [ 4 ] New: Critical [ 2 ]
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-24380 [ JENKINS-24380 ]
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Jesse Glick added a comment -

          Hmm, I definitely wrote (and tested) code to create <timestamp> in migrated build.xml records. Can you attach an example of the $JENKINS_HOME/jobs/*/builds/*/build.xml for one of the migrated builds showing a zero timestamp? Also if you happen to have your Jenkins log from the first startup after 1.597, attach that, in case there were any warnings. And attach the legacyIds file from the builds parent directory.

          Jesse Glick added a comment - Hmm, I definitely wrote (and tested) code to create <timestamp> in migrated build.xml records. Can you attach an example of the $JENKINS_HOME/jobs/*/builds/*/build.xml for one of the migrated builds showing a zero timestamp? Also if you happen to have your Jenkins log from the first startup after 1.597, attach that, in case there were any warnings. And attach the legacyIds file from the builds parent directory.

          Daniel Beck added a comment -

          tdtappe: Did you configure a nondefault build record directory in the global configuration? I.e. are the builds for a job NOT in .../job/foo/builds ?

          Daniel Beck added a comment - tdtappe: Did you configure a nondefault build record directory in the global configuration? I.e. are the builds for a job NOT in .../job/foo/builds ?

          Jesse Glick added a comment -

          Did you configure a nondefault build record directory in the global configuration?

          This should not matter, since the call to RunIdMigrator takes into account Job.getBuildDir, but of course this would be interesting information if so.

          (The reverse migration tool cannot handle nondefault build directories, unfortunately.)

          Jesse Glick added a comment - Did you configure a nondefault build record directory in the global configuration? This should not matter, since the call to RunIdMigrator takes into account Job.getBuildDir , but of course this would be interesting information if so. (The reverse migration tool cannot handle nondefault build directories, unfortunately.)

            jglick Jesse Glick
            tdtappe Heiko Tappe
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: