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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • 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

            vassilena Vassilena Treneva created issue -
            vassilena Vassilena Treneva made changes -
            Field Original Value New Value
            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 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
            vassilena Vassilena Treneva made changes -
            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
            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...
            basil Basil Crow made changes -
            Remote Link This issue links to "jenkinsci/timestamper-plugin#52 (Web Link)" [ 24527 ]
            basil Basil Crow made changes -
            Assignee Steven G Brown [ stevengbrown ] Basil Crow [ basil ]
            basil Basil Crow made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            basil Basil Crow made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            basil Basil Crow made changes -
            Link This issue relates to JENKINS-56457 [ JENKINS-56457 ]
            basil Basil Crow made changes -
            Resolution Fixed [ 1 ]
            Status In Review [ 10005 ] Fixed but Unreleased [ 10203 ]
            basil Basil Crow made changes -
            Released As 1.11.1
            Status Fixed but Unreleased [ 10203 ] Closed [ 6 ]
            basil Basil Crow made changes -
            Link This issue is duplicated by JENKINS-56457 [ JENKINS-56457 ]
            tkleiber Torsten Kleiber made changes -
            Resolution Fixed [ 1 ]
            Status Closed [ 6 ] Reopened [ 4 ]

              People

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

                Dates

                Created:
                Updated: