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

timestamper shows wrong time on [View as plain text] link

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: timestamper-plugin
    • Labels:
      None
    • Environment:
      CentOS Linux release 7.6.1810
      Jenkins ver. 2.195
      Timestamper plugin v1.10
    • Similar Issues:
    • Released As:
      1.11.1

      Description

      The plugin shows correct timestamp when looking at the [Console Output:

      2019-10-03 01:28:35 Started by upstream project "10.7_release_pipeline" build number 89
      2019-10-03 01:28:35 originally caused by:
      2019-10-03 01:28:35 Started by timer
      2019-10-03 01:28:36 Running in Durability level: PERFORMANCE_OPTIMIZED
      2019-10-03 01:28:42 [Pipeline] Start of Pipeline
      2019-10-03 01:28:42 [Pipeline] properties
      2019-10-03 01:28:43 [Pipeline] timestamps
      2019-10-03 01:28:43 The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds.
      2019-10-03 01:28:43 [Pipeline] {
      2019-10-03 01:28:43 [Pipeline] library
      2019-10-03 01:28:43 WARNING: Unknown parameter(s) found for class type 'jenkins.scm.impl.subversion.SubversionSCMSource': ignoreExternalsOption
      2019-10-03 01:28:43 Loading library templates@branches/rel/10.7.0.x/build/change-management/jenkinsfiles/templates

      But when looking at the same build instance using [View as plain text] the timestamp is wrong:

      [2019-10-02T22:28:35.925Z] Started by upstream project "10.7_release_pipeline" build number 89
      [2019-10-02T22:28:35.925Z] originally caused by:
      [2019-10-02T22:28:35.925Z] Started by timer
      [2019-10-02T22:28:36.043Z] Running in Durability level: PERFORMANCE_OPTIMIZED
      [2019-10-02T22:28:42.245Z] [Pipeline] Start of Pipeline
      [2019-10-02T22:28:42.703Z] [Pipeline] properties
      [2019-10-02T22:28:43.191Z] [Pipeline] timestamps
      [2019-10-02T22:28:43.191Z] The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds.
      [2019-10-02T22:28:43.192Z] [Pipeline] {
      [2019-10-02T22:28:43.404Z] [Pipeline] library
      [2019-10-02T22:28:43.416Z] WARNING: Unknown parameter(s) found for class type 'jenkins.scm.impl.subversion.SubversionSCMSource': ignoreExternalsOption
      [2019-10-02T22:28:43.448Z] Loading library templates@branches/rel/10.7.0.x/build/change-management/jenkinsfiles/templates

      The timestamper is enabled for all pipeline build and has the following formating: '<b>'yyyy-MM-dd HH:mm:ss'</b> ' which appears correct in the [Console Output] but not in [View as plain text]

      We have the following java argument added to our master configuration: JAVA_ARGS="-Dorg.apache.commons.jelly.tags.fmt.timeZone=Europe/Sofia"

       

      The hardware clock of the VM on which the master is hosted ouputs correct timing as well:

       

      sudo hwclock --show

      Thu 03 Oct 2019 10:03:11 AM EEST -0.355352 seconds

       

      date
      Thu Oct 3 10:04:14 EEST 2019

       

      I wonder where is the wrong timestamp read from?

      Perhaps, if I knew I would be able to work around the issue by changing some system settings. Browsing the console text with correct timestamps is quite important especially when you have big outputs in general...

        Attachments

          Issue Links

            Activity

            Hide
            slon4ik Eugene Koval added a comment -

            +1
            I guess the plain text log (shown by "View as plaint text" button) just shows the UTC time, while my Jenkins server system time is UTC+2.
            I understand the need to store one universal time (which then can be displayed differently for different users in different timezones), but that universal time has really got to be the Jenkins server system time, not UTC time.
            Reason: Jenkins time at least makes sense to Jenkins admins and has a chance of being intuitive for users ("this timestamp is wrong! => why? => maybe it's server time, not my time"), while UTC is meaningless for anyone who does not happen to live in UTC+0 timezone just by chance.

            Jenkins: 2.190.2
            Timestamper plugin: 1.10

            Show
            slon4ik Eugene Koval added a comment - +1 I guess the plain text log (shown by "View as plaint text" button) just shows the UTC time, while my Jenkins server system time is UTC+2. I understand the need to store one universal time (which then can be displayed differently for different users in different timezones), but that universal time has really got to be the Jenkins server system time, not UTC time. Reason: Jenkins time at least makes sense to Jenkins admins and has a chance of being intuitive for users ("this timestamp is wrong! => why? => maybe it's server time, not my time"), while UTC is meaningless for anyone who does not happen to live in UTC+0 timezone just by chance. Jenkins: 2.190.2 Timestamper plugin: 1.10
            Hide
            basil Basil Crow added a comment -

            This should be fixed in jenkinsci/timestamper-plugin#52.

            Show
            basil Basil Crow added a comment - This should be fixed in jenkinsci/timestamper-plugin#52 .
            Hide
            vassilena Vassilena Treneva added a comment -

            Basil Crow, which version of the plugin stands for 52? 

            We are currently using 1.10 and I see an update to 1.11 is available (so I am assuimg 52 maps to some other release version )

            Show
            vassilena Vassilena Treneva added a comment - Basil Crow , which version of the plugin stands for 52?  We are currently using 1.10 and I see an update to 1.11 is available (so I am assuimg 52 maps to some other release version )
            Hide
            basil Basil Crow added a comment -

            which version of the plugin stands for 52?

            jenkinsci/timestamper-plugin#52 has been merged but not yet released. I am planning to release a new version of Timestamper soon, at which point I will update this bug.

            Show
            basil Basil Crow added a comment - which version of the plugin stands for 52? jenkinsci/timestamper-plugin#52 has been merged but not yet released. I am planning to release a new version of Timestamper soon, at which point I will update this bug.
            Hide
            basil Basil Crow added a comment -

            Fixed as of jenkinsci/timestamper-plugin#52 (and previous dependent changes).

            Show
            basil Basil Crow added a comment - Fixed as of jenkinsci/timestamper-plugin#52 (and previous dependent changes).
            Hide
            basil Basil Crow added a comment -

            Released in Timestamper 1.11.1.

            Show
            basil Basil Crow added a comment - Released in Timestamper 1.11.1 .

              People

              • Assignee:
                basil Basil Crow
                Reporter:
                vassilena Vassilena Treneva
              • Votes:
                2 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: