• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None
    • Jenkins ver. 2.204.1
    • Jenkins 2.240

      It appears there is an issue with Jenkins displaying time. I have suffered from two issues of which the second is more problematic.

      When I started using Jenkins at $NEW_COMPANY I had configured my timezone to be Europe/Brussels (CEST). And while Jenkins reported time as CEST, the actual time shown was UTC.

      The below job was started at 11:36 CEST !

      I assumed there was a timezone/time misconfiguration on the Jenkins server itself. After reporting we started to play around with the settings. I believed when changing my user timezone to Etc/UTC I would see a reported time with 2 hours behind. But lo and behold, the UTC time was the same (and correctly so) reported as UTC.

      So no problem for people living in a UTC timezone. However when going back to timezone Europe/Brussels, now the behavior was different:

      On initial refresh of the page all times were correct displaying the correct timezone. However a second later the time is updated using UTC time and CEST reported as timezone.

      So I experienced 2 problems, of which the second is worse as there appears no corrective action.

      • After initially setting up the correct timezone, all reported times where UTC while reporting the (user configured) CEST timezone (so 2 hours behind real time)
      • When switching to UTC and back to CEST, only the running jobs are showing UTC time with a report CEST timezone

          [JENKINS-61972] Time is wrongly displayed on running Jobs

          Dag Wieers created issue -
          Dag Wieers made changes -
          Attachment New: Screenshot from 2020-04-20 12-36-36.png [ 50999 ]

          Dag Wieers added a comment -

          I can actually reproduce this issue on ci.jenkins.io !

          https://ci.jenkins.io/job/Infra/job/jenkins.io/job/PR-3084/

          The below job was started at 12:31 AM CEST, and it was reported correctly and quickly replaced with the wrong UTC time.

          Dag Wieers added a comment - I can actually reproduce this issue on ci.jenkins.io ! https://ci.jenkins.io/job/Infra/job/jenkins.io/job/PR-3084/ The below job was started at 12:31 AM CEST, and it was reported correctly and quickly replaced with the wrong UTC time.
          Dag Wieers made changes -
          Attachment New: Screencast from 20-04-20 131414.webm [ 51001 ]
          Dag Wieers made changes -
          Attachment New: Screencast from 20-04-20 131437.webm [ 51002 ]
          Dag Wieers made changes -
          Comment [ I recorded a small video with the issue happening when reloading the page.

          [^Screencast from 20-04-20 13:14:37.webm] ]
          Dag Wieers made changes -
          Attachment Original: Screencast from 20-04-20 131437.webm [ 51002 ]
          Dag Wieers made changes -
          Attachment Original: Screencast from 20-04-20 131414.webm [ 51001 ]
          Dag Wieers made changes -
          Comment [ I recorded a small video with the issue happening when reloading the page.

          [^Screencast from 20-04-20 131437.webm] ]

          Jesse Glick added a comment -

          danielbeck says this is due to JENKINS-19887.

          Jesse Glick added a comment - danielbeck says this is due to JENKINS-19887 .
          Jesse Glick made changes -
          Link New: This issue is caused by JENKINS-19887 [ JENKINS-19887 ]

            dag Dag Wieers
            dag Dag Wieers
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: