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

Build records get confused by timezone changes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Component/s: core
    • Labels:
      None
    • Environment:
      1.509.2
    • Similar Issues:

      Description

      A continuation of the travails from JENKINS-15816. If the timezone is changed after startup, it can happen that a job has some older builds with the old timezone that appear newer than the actually newest builds. Thus the RunMap gives an inconsistent picture (rm.values().iterator().next() != rm.iterator().next()), the last build may be older than the last successful build, BuildHistoryWidget may omit builds, etc.

      The proper fix is perhaps to start using UTC for build records and switch to a new Run.id format that ends with Z or otherwise distinguishes builds created after the switch from historical builds. The question is what plugin code might be relying on the current format.

        Attachments

          Issue Links

            Activity

            Hide
            jglick Jesse Glick added a comment -

            Either 1376 or 1379 would fix this.

            Show
            jglick Jesse Glick added a comment - Either 1376 or 1379 would fix this.
            Hide
            jglick Jesse Glick added a comment -

            The fix of JENKINS-24380 should cover this.

            Show
            jglick Jesse Glick added a comment - The fix of JENKINS-24380 should cover this.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              jglick Jesse Glick
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: