-
Improvement
-
Resolution: Fixed
-
Major
-
None
The Timestamper plugin currently inserts a console note into every line of the build's log file. Console notes are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. This is necessary to support features such as the timestamp format setting.
Inserting a console note into every line, as the Timestamper plugin does, increases the size of the log file and makes the file more difficult to read in a text editor.
Arguably, it may also make it more difficult for external tools (scripts and other plugins) to parse the console log. Although Jenkins will already insert console notes without the Timestamper plugin installed, the Timestamper plugin inserts many more of them and so it has exposed bugs in other plugins.
It would be nice to store the timestamps in a separate file to the console, and in a more efficient format. The Timestamper plugin would still need a way to insert these timestamps back into the console when it is being viewed in Jenkins.
Unfortunately, this alternate solution will be much more time-consuming to implement than the console notes solution.
Backwards compatibility:
- The Timestamper plugin should retain the ability to display existing console notes.
- There should be an option to still use console notes, because a few people have written scripts to read them from the log file.
- The /timestamps URL (introduced in version 1.3.2) must continue to read the console notes when this option has been selected.
[JENKINS-14932] Compact encoding for timestamps, alternative to console note encoding
Steven G Brown
created issue -
Steven G Brown
made changes -
| Description |
Original:
Replace console notes with a different mechanism, in order to make the log files more readable and easier to parse with scripts. * The [console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. Any alternative solution also needs to support formatting at view time. * Inserting a console note into every line, as the Timestamper plugin does, has several disadvantages: *- They increase the file size of the log. *- They make the log file more difficult to read in a text editor. *- External scripts may need to skip over the console notes when reading the log file. (Jenkins itself and the Jenkins plugins already need to deal with console notes, so they are not really affected.) *- They make it difficult to read the times with a script, e.g. to determine which parts of the build are the slowest. * It would be nice to store the elapsed time instead of a console note, in hhmmss format. The Timestamper plugin would need to replace these timestamps when Jenkins displays the console log. This may require changes to Jenkins core. * The Timestamper plugin should to retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from log. |
New:
Instead of relying on console notes, store the timestamps in a more compact and human-readable format. The [console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. Any alternative solution also needs to support formatting at view time. Inserting a console note into every line, as the Timestamper plugin does, has several disadvantages: - They increase the file size of the log. - They make the log file more difficult to read in a text editor. - External scripts may need to skip over the console notes when reading the log file. (Jenkins itself and the Jenkins plugins already need to deal with console notes, so they are not as much of a concern.) - They make it difficult to read the times with a script, e.g. to determine which parts of the build are the slowest. It would be nice to store the timestamps as the elapsed time since the build started in hhmmss format. The Timestamper plugin would need to replace these timestamps when Jenkins displays the console log. This may require changes to Jenkins core. Backwards compatibility: * The Timestamper plugin should to retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from the log file. |
Steven G Brown
made changes -
| Description |
Original:
Instead of relying on console notes, store the timestamps in a more compact and human-readable format. The [console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. Any alternative solution also needs to support formatting at view time. Inserting a console note into every line, as the Timestamper plugin does, has several disadvantages: - They increase the file size of the log. - They make the log file more difficult to read in a text editor. - External scripts may need to skip over the console notes when reading the log file. (Jenkins itself and the Jenkins plugins already need to deal with console notes, so they are not as much of a concern.) - They make it difficult to read the times with a script, e.g. to determine which parts of the build are the slowest. It would be nice to store the timestamps as the elapsed time since the build started in hhmmss format. The Timestamper plugin would need to replace these timestamps when Jenkins displays the console log. This may require changes to Jenkins core. Backwards compatibility: * The Timestamper plugin should to retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from the log file. |
New:
Instead of relying on console notes, store the timestamps in a more compact and human-readable format. The [console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. Any alternative solution also needs to support formatting at view time. Inserting a console note into every line, as the Timestamper plugin does, has several disadvantages: - They increase the file size of the log. - They make the log file more difficult to read in a text editor. - External scripts may need to skip over the console notes when reading the log file. (Jenkins itself and the Jenkins plugins already need to deal with console notes, so they are not as much of a concern.) - They make it difficult to read the times with a script, e.g. to determine which parts of the build are the slowest. It would be nice to store the timestamps as the number of elapsed milliseconds since the build started. The Timestamper plugin would need to replace these timestamps when Jenkins displays the console log. This may require changes to Jenkins core. Backwards compatibility: * The Timestamper plugin should to retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from the log file. |
Steven G Brown
made changes -
| Description |
Original:
Instead of relying on console notes, store the timestamps in a more compact and human-readable format. The [console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. Any alternative solution also needs to support formatting at view time. Inserting a console note into every line, as the Timestamper plugin does, has several disadvantages: - They increase the file size of the log. - They make the log file more difficult to read in a text editor. - External scripts may need to skip over the console notes when reading the log file. (Jenkins itself and the Jenkins plugins already need to deal with console notes, so they are not as much of a concern.) - They make it difficult to read the times with a script, e.g. to determine which parts of the build are the slowest. It would be nice to store the timestamps as the number of elapsed milliseconds since the build started. The Timestamper plugin would need to replace these timestamps when Jenkins displays the console log. This may require changes to Jenkins core. Backwards compatibility: * The Timestamper plugin should to retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from the log file. |
New:
The Timestamper plugin currently inserts a console note into every line of the build's log file. [Console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. Any alternative solution also needs to support formatting at view time. Inserting a console note into every line, as the Timestamper plugin does, has several disadvantages: - They increase the file size of the log. - They make the log file more difficult to read in a text editor. - External scripts may need to skip over the console notes when reading the log file. (Jenkins itself and the Jenkins plugins already need to deal with console notes, so they are not as much of a concern.) - They make it difficult to read the times with a script, e.g. to determine which parts of the build are the slowest. It would be nice to store the timestamps in a separate file to the console, and in a more efficient format. The Timestamper plugin would still need a way to insert these timestamps back into the console when it is being viewed in Jenkins. Backwards compatibility: * The Timestamper plugin should to retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from the log file. * The /timestamps URL (introduced in version 1.3.2) must continue to read the console notes when this option has been selected. |
Steven G Brown
made changes -
| Description |
Original:
The Timestamper plugin currently inserts a console note into every line of the build's log file. [Console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. Any alternative solution also needs to support formatting at view time. Inserting a console note into every line, as the Timestamper plugin does, has several disadvantages: - They increase the file size of the log. - They make the log file more difficult to read in a text editor. - External scripts may need to skip over the console notes when reading the log file. (Jenkins itself and the Jenkins plugins already need to deal with console notes, so they are not as much of a concern.) - They make it difficult to read the times with a script, e.g. to determine which parts of the build are the slowest. It would be nice to store the timestamps in a separate file to the console, and in a more efficient format. The Timestamper plugin would still need a way to insert these timestamps back into the console when it is being viewed in Jenkins. Backwards compatibility: * The Timestamper plugin should to retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from the log file. * The /timestamps URL (introduced in version 1.3.2) must continue to read the console notes when this option has been selected. |
New:
The Timestamper plugin currently inserts a console note into every line of the build's log file. [Console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. Any alternative solution also needs to support formatting at view time. Inserting a console note into every line, as the Timestamper plugin does, increases the size of the log file and makes the file more difficult to read in a text editor. It would be nice to store the timestamps in a separate file to the console, and in a more efficient format. The Timestamper plugin would still need a way to insert these timestamps back into the console when it is being viewed in Jenkins. Backwards compatibility: * The Timestamper plugin should to retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from the log file. * The /timestamps URL (introduced in version 1.3.2) must continue to read the console notes when this option has been selected. |
Steven G Brown
made changes -
| Description |
Original:
The Timestamper plugin currently inserts a console note into every line of the build's log file. [Console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. Any alternative solution also needs to support formatting at view time. Inserting a console note into every line, as the Timestamper plugin does, increases the size of the log file and makes the file more difficult to read in a text editor. It would be nice to store the timestamps in a separate file to the console, and in a more efficient format. The Timestamper plugin would still need a way to insert these timestamps back into the console when it is being viewed in Jenkins. Backwards compatibility: * The Timestamper plugin should to retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from the log file. * The /timestamps URL (introduced in version 1.3.2) must continue to read the console notes when this option has been selected. |
New:
The Timestamper plugin currently inserts a console note into every line of the build's log file. [Console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. Any alternative solution also needs to support formatting at view time. Inserting a console note into every line, as the Timestamper plugin does, increases the size of the log file and makes the file more difficult to read in a text editor. Arguably, it may also make it more difficult for external tools (scripts and other plugins) to parse the console log. Although Jenkins will already insert console notes without the Timestamper plugin installed, the Timestamper plugin inserts many more of them and so it has exposed bugs in other plugins. It would be nice to store the timestamps in a separate file to the console, and in a more efficient format. The Timestamper plugin would still need a way to insert these timestamps back into the console when it is being viewed in Jenkins. Backwards compatibility: * The Timestamper plugin should to retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from the log file. * The /timestamps URL (introduced in version 1.3.2) must continue to read the console notes when this option has been selected. |
Steven G Brown
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Steven G Brown
made changes -
| Description |
Original:
The Timestamper plugin currently inserts a console note into every line of the build's log file. [Console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. Any alternative solution also needs to support formatting at view time. Inserting a console note into every line, as the Timestamper plugin does, increases the size of the log file and makes the file more difficult to read in a text editor. Arguably, it may also make it more difficult for external tools (scripts and other plugins) to parse the console log. Although Jenkins will already insert console notes without the Timestamper plugin installed, the Timestamper plugin inserts many more of them and so it has exposed bugs in other plugins. It would be nice to store the timestamps in a separate file to the console, and in a more efficient format. The Timestamper plugin would still need a way to insert these timestamps back into the console when it is being viewed in Jenkins. Backwards compatibility: * The Timestamper plugin should to retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from the log file. * The /timestamps URL (introduced in version 1.3.2) must continue to read the console notes when this option has been selected. |
New:
The Timestamper plugin currently inserts a console note into every line of the build's log file. [Console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. This is necessary to support features such as the timestamp format setting. Inserting a console note into every line, as the Timestamper plugin does, increases the size of the log file and makes the file more difficult to read in a text editor. Arguably, it may also make it more difficult for external tools (scripts and other plugins) to parse the console log. Although Jenkins will already insert console notes without the Timestamper plugin installed, the Timestamper plugin inserts many more of them and so it has exposed bugs in other plugins. It would be nice to store the timestamps in a separate file to the console, and in a more efficient format. The Timestamper plugin would still need a way to insert these timestamps back into the console when it is being viewed in Jenkins. Unfortunately, this alternate solution will be much more time-consuming to implement than the console notes solution. Backwards compatibility: * The Timestamper plugin should to retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from the log file. * The /timestamps URL (introduced in version 1.3.2) must continue to read the console notes when this option has been selected. |
Steven G Brown
made changes -
| Description |
Original:
The Timestamper plugin currently inserts a console note into every line of the build's log file. [Console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. This is necessary to support features such as the timestamp format setting. Inserting a console note into every line, as the Timestamper plugin does, increases the size of the log file and makes the file more difficult to read in a text editor. Arguably, it may also make it more difficult for external tools (scripts and other plugins) to parse the console log. Although Jenkins will already insert console notes without the Timestamper plugin installed, the Timestamper plugin inserts many more of them and so it has exposed bugs in other plugins. It would be nice to store the timestamps in a separate file to the console, and in a more efficient format. The Timestamper plugin would still need a way to insert these timestamps back into the console when it is being viewed in Jenkins. Unfortunately, this alternate solution will be much more time-consuming to implement than the console notes solution. Backwards compatibility: * The Timestamper plugin should to retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from the log file. * The /timestamps URL (introduced in version 1.3.2) must continue to read the console notes when this option has been selected. |
New:
The Timestamper plugin currently inserts a console note into every line of the build's log file. [Console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. This is necessary to support features such as the timestamp format setting. Inserting a console note into every line, as the Timestamper plugin does, increases the size of the log file and makes the file more difficult to read in a text editor. Arguably, it may also make it more difficult for external tools (scripts and other plugins) to parse the console log. Although Jenkins will already insert console notes without the Timestamper plugin installed, the Timestamper plugin inserts many more of them and so it has exposed bugs in other plugins. It would be nice to store the timestamps in a separate file to the console, and in a more efficient format. The Timestamper plugin would still need a way to insert these timestamps back into the console when it is being viewed in Jenkins. Unfortunately, this alternate solution will be much more time-consuming to implement than the console notes solution. Backwards compatibility: * The Timestamper plugin should retain the ability to display existing console notes. * There should be an option to still use console notes, because a few people have written scripts to read them from the log file. * The /timestamps URL (introduced in version 1.3.2) must continue to read the console notes when this option has been selected. |
Steven G Brown
made changes -
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JNJira [ 145633 ] | New: JNJira + In-Review [ 206089 ] |