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

"System Time" ignores the TimeZone

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I have Jenkins started with -Dorg.apache.commons.jelly.tags.fmt.timeZone="America/Los_Angeles"

      The server's TZ is EDT (it's in Pittsburgh).

      However, the "System Clock" setting for the TimeStamper is showing EDT time, not PDT.

      It should be using the passed in TimeZone.

        Attachments

          Activity

          Hide
          generatz Generic Ratslaugh added a comment - - edited

          I'm having a related problem: my Jenkins timestamp 'System clock time' appears to be unadjusted for daylight savings time. I'm using RHEL 6.5, and the Jenkins timestamp is currently 1 hour earlier than what I get from `date` command on CLI. Aside from this timestamp, most of the other times in Jenkins are correct, though my mercurial "Multiple SCMs Polling Log" time are also off by one hour. (BTW, I otherwise love this plugin - much thanks.)

          Show
          generatz Generic Ratslaugh added a comment - - edited I'm having a related problem: my Jenkins timestamp 'System clock time' appears to be unadjusted for daylight savings time. I'm using RHEL 6.5, and the Jenkins timestamp is currently 1 hour earlier than what I get from `date` command on CLI. Aside from this timestamp, most of the other times in Jenkins are correct, though my mercurial "Multiple SCMs Polling Log" time are also off by one hour. (BTW, I otherwise love this plugin - much thanks.)
          Hide
          generatz Generic Ratslaugh added a comment -

          I just discovered this issue on my system: http://www.iwasdot.com/?p=6
          /etc/sysconfig/clock incorrectly had
          ZONE="America/New York"
          and needed to be corrected to
          ZONE="America/New_York"

          That fixed everything for me.

          Show
          generatz Generic Ratslaugh added a comment - I just discovered this issue on my system: http://www.iwasdot.com/?p=6 /etc/sysconfig/clock incorrectly had ZONE="America/New York" and needed to be corrected to ZONE="America/New_York" That fixed everything for me.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Steven Brown
          Path:
          src/main/java/hudson/plugins/timestamper/TimestamperConfig.java
          src/main/java/hudson/plugins/timestamper/format/TimestampFormatterImpl.java
          src/test/java/hudson/plugins/timestamper/format/TimestampFormatterImplTest.java
          http://jenkins-ci.org/commit/timestamper-plugin/033dea207abef18a3f564ba5571ebee65ea58f50
          Log:
          [FIXED JENKINS-22586]

          Respond to system parameter "org.apache.commons.jelly.tags.fmt.timeZone"

          See https://wiki.jenkins-ci.org/display/JENKINS/Change+time+zone

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Steven Brown Path: src/main/java/hudson/plugins/timestamper/TimestamperConfig.java src/main/java/hudson/plugins/timestamper/format/TimestampFormatterImpl.java src/test/java/hudson/plugins/timestamper/format/TimestampFormatterImplTest.java http://jenkins-ci.org/commit/timestamper-plugin/033dea207abef18a3f564ba5571ebee65ea58f50 Log: [FIXED JENKINS-22586] Respond to system parameter "org.apache.commons.jelly.tags.fmt.timeZone" See https://wiki.jenkins-ci.org/display/JENKINS/Change+time+zone

            People

            • Assignee:
              stevengbrown Steven G Brown
              Reporter:
              docwhat Christian Höltje
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: