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

Build records get confused by timezone changes

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Duplicate
    • core
    • None
    • 1.509.2

    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

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-15816 Run.ID_FORMATTER caches stale timezone values

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-24376 Queue constantly locked when rapidly scheduling builds

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-22106 @midnight is vulnerable to DST witching hours

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Task - A task that needs to be done. JENKINS-24380 Use build numbers as IDs

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link PR 1376

          Activity

            Ascending order - Click to sort in descending order
            jglick Jesse Glick added a comment -

            Either 1376 or 1379 would fix this.

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

            The fix of JENKINS-24380 should cover this.

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

            People

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

              Dates

                Created:
                Updated:
                Resolved: