-
New Feature
-
Resolution: Duplicate
-
Minor
-
None
-
Jenkins 2.7.4
Timestamp plugin 1.8.7
Although the source documentation indicates otherwise, it appears that the encoded timestamps are always being inserted directly into the console log files leading to difficulty parsing files from disk.
/**
* Time-stamp console note.
* <p>
* These are inserted into the log file when:
* <ul>
* <li>The build does not extend {@link AbstractBuild}, e.g. a pipeline job.</li>
* <li>Running the Timestamper plugin prior to version 1.4.</li>
* <li>The system property is set: ({@link #getSystemProperty()}). The is
* intended to support scripts that were written prior to Timestamper 1.4 to
* parse the log files. New scripts should query the {@code /timestamps} URL
* instead (see {@link TimestampsAction}).</li>
* </ul>
* <p>
* Otherwise, the time-stamps are stored in a separate file, which allows a more
* compact format to be used and avoids filling the log files with encoded
* console notes.
*
* @author Steven G. Brown
*/
Seem to indicate that a pipeline job using recent versions of the plugin should not have this issue. But the system property is checked as a boolean and since TimeStampNote.getSystemProperty() always returns a string its always true.
- duplicates
-
JENKINS-48344 Log files generated by Jenkins pipeline scripts are bloated
-
- Resolved
-
- is related to
-
-
- Open
-
