[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link

17 views
Skip to first unread message

vasilena.treneva@softwareag.com (JIRA)

unread,
Oct 3, 2019, 3:01:03 AM10/3/19
to jenkinsc...@googlegroups.com
Vassilena Treneva created an issue
 
Jenkins / Bug JENKINS-59636
timestamper shows wrong time on [View as plain text] link
Issue Type: Bug Bug
Assignee: Steven G Brown
Components: timestamper-plugin
Created: 2019-10-03 07:00
Environment: CentOS Linux release 7.6.1810
Jenkins ver. 2.195
Timestamper plugin v1.10
Priority: Major Major
Reporter: Vassilena Treneva

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"

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

vasilena.treneva@softwareag.com (JIRA)

unread,
Oct 3, 2019, 3:05:04 AM10/3/19
to jenkinsc...@googlegroups.com
Vassilena Treneva updated an issue
Change By: Vassilena Treneva


 

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

vasilena.treneva@softwareag.com (JIRA)

unread,
Oct 3, 2019, 3:09:05 AM10/3/19
to jenkinsc...@googlegroups.com


 

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...

koval.gene@gmail.com (JIRA)

unread,
Nov 19, 2019, 11:35:02 AM11/19/19
to jenkinsc...@googlegroups.com
Eugene Koval commented on Bug JENKINS-59636
 
Re: timestamper shows wrong time on [View as plain text] link

+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

me@basilcrow.com (JIRA)

unread,
Feb 25, 2020, 9:21:03 PM2/25/20
to jenkinsc...@googlegroups.com

me@basilcrow.com (JIRA)

unread,
Feb 25, 2020, 9:21:05 PM2/25/20
to jenkinsc...@googlegroups.com

me@basilcrow.com (JIRA)

unread,
Feb 25, 2020, 9:21:05 PM2/25/20
to jenkinsc...@googlegroups.com
Basil Crow assigned an issue to Basil Crow
Change By: Basil Crow
Assignee: Steven G Brown Basil Crow

me@basilcrow.com (JIRA)

unread,
Feb 25, 2020, 9:21:06 PM2/25/20
to jenkinsc...@googlegroups.com
Basil Crow started work on Bug JENKINS-59636
 
Change By: Basil Crow
Status: Open In Progress

vasilena.treneva@softwareag.com (JIRA)

unread,
Feb 26, 2020, 3:20:02 AM2/26/20
to jenkinsc...@googlegroups.com
Vassilena Treneva commented on Bug JENKINS-59636
 
Re: timestamper shows wrong time on [View as plain text] link

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 )

me@basilcrow.com (JIRA)

unread,
Feb 26, 2020, 11:31:06 AM2/26/20
to jenkinsc...@googlegroups.com

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.

me@basilcrow.com (JIRA)

unread,
Feb 26, 2020, 2:25:03 PM2/26/20
to jenkinsc...@googlegroups.com
 

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

Change By: Basil Crow
Status: In Review Fixed but Unreleased
Resolution: Fixed
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

me@basilcrow.com (JIRA)

unread,
Mar 3, 2020, 11:02:03 AM3/3/20
to jenkinsc...@googlegroups.com
 

Released in Timestamper 1.11.1.

Change By: Basil Crow
Status: Fixed but Unreleased Closed
Released As: 1.11.1
Reply all
Reply to author
Forward
0 new messages