• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None
    • Server: Windows Server 2008 R2, Tomcat 6.0.20, JDK 1.6.0_20, Hudson 1.357
      Client: Windows 7 Enterprise, Google Chrome 5.0

      When viewing a job, the timeline displays times using GMT rather than the server's timezone — EDT (GMT-0400) in my case. This means that a build which took place at 12:57 PM shows up right before "17h" on the timeline, but it should appear right before "13h" (see attached screenshot).

        1. JENKINS-6692.png
          28 kB
          Mark Lewis
        2. timeline-timezone.png
          28 kB
          Mark Lewis

          [JENKINS-6692] Timeline should use server's timezone, not GMT

          Code changed in hudson
          User: : mindless
          Path:
          trunk/hudson/main/core/src/main/resources/hudson/model/Job/buildTimeTrend.jelly
          trunk/www/changelog.html
          http://jenkins-ci.org/commit/31945
          Log:
          [FIXED JENKINS-6692] Timeline on build trend page should use server timezone
          instead of always GMT.

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : mindless Path: trunk/hudson/main/core/src/main/resources/hudson/model/Job/buildTimeTrend.jelly trunk/www/changelog.html http://jenkins-ci.org/commit/31945 Log: [FIXED JENKINS-6692] Timeline on build trend page should use server timezone instead of always GMT.

          macosgrove added a comment -

          I'm still seeing this issue in Hudson 1.373, server and client both Windows XP Professional SP3.

          macosgrove added a comment - I'm still seeing this issue in Hudson 1.373, server and client both Windows XP Professional SP3.

          Sorin Sbarnea added a comment -

          And now the question is how do I force hudson to use GMT and military dateformat?

          Sorin Sbarnea added a comment - And now the question is how do I force hudson to use GMT and military dateformat?

          Mark Lewis added a comment -

          I am still seeing this problem in Jenkins 1.421. It's only 1 hour off now, so perhaps it is related to DST.

          Mark Lewis added a comment - I am still seeing this problem in Jenkins 1.421. It's only 1 hour off now, so perhaps it is related to DST.

          Still seeing this in 1.450. Time is 1 hour back.

          andrey regentov added a comment - Still seeing this in 1.450. Time is 1 hour back.

            mindless Alan Harder
            malfunction84 Mark Lewis
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: