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

Plain text timing entries in build log file

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Won't Fix
    • Icon: Major Major
    • timestamper-plugin
    • None

      Add plain text timestamp entries to the build log file (filesystem, not UI). This feature is intended to be used by external log parsers which require some timing information easily parseable.

      This feature is deactivated by default and must be activated by setting a system property.

          [JENKINS-30351] Plain text timing entries in build log file

          Antonio Muñiz created issue -
          Antonio Muñiz made changes -
          Assignee Original: Steven G Brown [ stevengbrown ] New: Antonio Muñiz [ amuniz ]
          Antonio Muñiz made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Antonio Muñiz added a comment -

          PR sent: https://github.com/jenkinsci/timestamper-plugin/pull/16

          Antonio Muñiz added a comment - PR sent: https://github.com/jenkinsci/timestamper-plugin/pull/16

          Jesse Glick added a comment -

          Seems like a poor approach to me. What are these external parsers? And why can they not use the standard Jenkins consoleText REST API?

          Jesse Glick added a comment - Seems like a poor approach to me. What are these external parsers? And why can they not use the standard Jenkins consoleText REST API?

          Antonio Muñiz added a comment -

          Why do you think it's poor? It's simply an additional feature.
          I'm thinking about log data extract and aggregation tools like Splunk, Awstats or Scribe.

          Antonio Muñiz added a comment - Why do you think it's poor? It's simply an additional feature. I'm thinking about log data extract and aggregation tools like Splunk, Awstats or Scribe.

          Steven G Brown added a comment -

          I'm not keen on this either. Putting the timestamps into the log file breaks most features of the plugin: it is no longer possible to see the elapsed time, turn the timestamps off, change the time-zone, or configure the time-stamp format after the build has completed (which becomes more important when JENKINS-18826 is implemented.)

          The /timestamps URL is intended to provide the timestamps for use by external tools. If it doesn't provide the format that you need, you could consider adding another query parameter.
          https://wiki.jenkins-ci.org/display/JENKINS/Timestamper#Timestamper-Scripting

          Steven G Brown added a comment - I'm not keen on this either. Putting the timestamps into the log file breaks most features of the plugin: it is no longer possible to see the elapsed time, turn the timestamps off, change the time-zone, or configure the time-stamp format after the build has completed (which becomes more important when JENKINS-18826 is implemented.) The /timestamps URL is intended to provide the timestamps for use by external tools. If it doesn't provide the format that you need, you could consider adding another query parameter. https://wiki.jenkins-ci.org/display/JENKINS/Timestamper#Timestamper-Scripting

          Antonio Muñiz added a comment -

          jglick The consoleText API does not include timestamps generated by this plugin, so it's not an option.
          stevengbrown /timestamps API would require two HTTP requests from a external tool (one to consoleText and a second one to /timestamps) which is a weird way to get a simple log file with timestamps (and probably not doable with most of the log analysis tools, which require direct access to the log file).

          The proposed PR didn't break anything, since the time selector menu is hidden when you use -Dtimestamper-consolenotes-plain=true, so the user would be who decides if he wants the full feature set or a plain timestamp in the log file (which is the most common use case in the Java world).

          I'm missing this feature, but... your plugin, your rules, of course.

          Antonio Muñiz added a comment - jglick The consoleText API does not include timestamps generated by this plugin, so it's not an option. stevengbrown /timestamps API would require two HTTP requests from a external tool (one to consoleText and a second one to /timestamps ) which is a weird way to get a simple log file with timestamps (and probably not doable with most of the log analysis tools, which require direct access to the log file). The proposed PR didn't break anything, since the time selector menu is hidden when you use -Dtimestamper-consolenotes-plain=true , so the user would be who decides if he wants the full feature set or a plain timestamp in the log file (which is the most common use case in the Java world). I'm missing this feature, but... your plugin, your rules, of course.

          Antonio Muñiz added a comment -

          Closing this issue as the proposed PR was rejected by stevengbrown

          Antonio Muñiz added a comment - Closing this issue as the proposed PR was rejected by stevengbrown

            amuniz Antonio Muñiz
            amuniz Antonio Muñiz
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: