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

Inconsitent timstamp precision

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • influxdb-plugin
    • None
    • Jenkins ver. 2.121.3
      Influxdb-plugin ver. 1.19

      Im a bit confused about whats the timestamp precision for build_exec_time, build_measured_time and build_time.

      According to the data in influxdb, build_exec_time, build_measured_time are picoseconds, and build_time is attosecond. (the test pipeline job finished around 1.5s)

      Am I misunderstood something ?

       

      > SELECT build_exec_time,build_measured_time FROM jenkins_data;
name: jenkins_data
time build_exec_time build_measured_time
---- --------------- -------------------
2018-09-12T10:21:11.168Z 1536747667886 1536747671178

> SELECT build_time FROM jenkins_custom_data;
name: jenkins_custom_data
time build_time
---- ----------
2018-09-12T10:21:11.168Z 1536746134420332137

          [JENKINS-53524] Inconsitent timstamp precision

          Aleksi Simell added a comment - - edited

          Build_exec_time gets it's value straight from getStartTimeInMillis(), build_measured_time is from currentTimeMillis() and build_time is either gets the data straight from getDuration() (non-pipeline jobs) or a subtraction from currentTimeMillis() and getTimeInMillis() (pipeline jobs). All these are "long" datatype from Java and the precision is not declared.

          Aleksi Simell added a comment - - edited Build_exec_time gets it's value straight from getStartTimeInMillis() , build_measured_time is from currentTimeMillis()  and build_time is either gets the data straight from getDuration()  (non-pipeline jobs) or a subtraction from currentTimeMillis() and  getTimeInMillis()  (pipeline jobs). All these are "long" datatype from Java and the precision is not declared.

          Zsolt Nagy added a comment -

          Thanks for clarifying it.

          Looks like something changed in 1.18 in the custom_data, build_time which caused Grafana showing incorrect times from builds.

          Thanks Again.

          Zsolt Nagy added a comment - Thanks for clarifying it. Looks like something changed in 1.18 in the custom_data, build_time which caused Grafana showing incorrect times from builds. Thanks Again.

            aleksisimell Aleksi Simell
            ztg Zsolt Nagy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: