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

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

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • timestamper-plugin
    • None
    • CentOS Linux release 7.6.1810
      Jenkins ver. 2.195
      Timestamper plugin v1.10
    • 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

            basil Basil Crow added a comment -

            Released in Timestamper 1.11.1.

            basil Basil Crow added a comment - Released in Timestamper 1.11.1 .
            zhongjun2020 You added a comment - - edited

            I am feeling this issue has not fixed yet.  vassilena  did you get it ?

            from job/389ab143-51b5-4494-a6de-d4de82afe331/40/logText/progressiveText

            still UTC time, even if I set time as local time.  jenkins console and jenkins system logs show correct time. but from logText/progressiveText and blueocean view,  they are showing UTC time

             

            jenkins: 2.235.5

            timestamper : 1.11.5

            zhongjun2020 You added a comment - - edited I am feeling this issue has not fixed yet.  vassilena   did you get it ? from job/389ab143-51b5-4494-a6de-d4de82afe331/40/logText/progressiveText still UTC time, even if I set time as local time.  jenkins console and jenkins system logs show correct time. but from logText/progressiveText and blueocean view,  they are showing UTC time   jenkins: 2.235.5 timestamper : 1.11.5
            tkleiber Torsten Kleiber added a comment - - edited

            Still wrong (UTC) in blue ocean with timestamper 1.13 and Jenkins LTS 2.289.1.

            tkleiber Torsten Kleiber added a comment - - edited Still wrong (UTC) in blue ocean with timestamper 1.13 and Jenkins LTS 2.289.1.
            richmond Rich added a comment -

            Using version 1.17 and I still see wrong timezone in [View as plain text]. Is there any workaround available ?

            richmond Rich added a comment - Using version 1.17 and I still see wrong timezone in [View as plain text] . Is there any workaround available ?
            basil Basil Crow added a comment -

            If there is still a problem, please open a new ticket with steps to reproduce the issue from scratch on a clean installation.

            basil Basil Crow added a comment - If there is still a problem, please open a new ticket with steps to reproduce the issue from scratch on a clean installation.

            People

              basil Basil Crow
              vassilena Vassilena Treneva
              Votes:
              5 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: