[JIRA] (JENKINS-40605) Time reported is not correct

[tscher...@cloudbees.com (JIRA)]

Title: Message Title

Thorsten Scherler commented on JENKINS-40605   Re: Time reported is not correct Hmm, that is a tricky one. We use the server timestamp indeed for both times in the header. const durationMillis = run.isRunning() ? moment().diff(moment(run.startTime)) : run.durationInMillis; ... <ReadableDate date={run.endTime} liveUpdate locale={locale} shortFormat={t('common.date.readable.short', { defaultValue: 'MMM DD h:mma Z' })} longFormat={t('common.date.readable.long', { defaultValue: 'MMM DD YYYY h:mma Z' })} /> I think I have to read the http response header to see when the server answers and then compare that with local time. In case they are different I need to adopt the above `startTime` and `endTime` Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.