[JIRA] (JENKINS-14932) Compact encoding for timestamps, alternative to console note encoding
stevengbrown closed JENKINS-14932 as Fixed Compact encoding for timestamps, alternative to console note encoding Change By: stevengbrown (02/Feb/13 2:26 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-14932) Compact encoding for timestamps, alternative to console note encoding
stevengbrown updated JENKINS-14932 Compact encoding for timestamps, alternative to console note encoding Change By: stevengbrown (05/Jan/13 3:18 AM) Description: 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. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14932) Compact encoding for timestamps, alternative to console note encoding
stevengbrown updated JENKINS-14932 Compact encoding for timestamps, alternative to console note encoding Change By: stevengbrown (27/Dec/12 10:02 AM) Description: 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 This is necessary to support formatting at view time 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. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14932) Compact encoding for timestamps, alternative to console note encoding
stevengbrown resolved JENKINS-14932 as Fixed Compact encoding for timestamps, alternative to console note encoding Released with Timestamper 1.4. Change By: stevengbrown (27/Dec/12 9:50 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14932) Compact encoding for timestamps, alternative to console note encoding
stevengbrown commented on JENKINS-14932 Compact encoding for timestamps, alternative to console note encoding Implemented by https://github.com/jenkinsci/timestamper-plugin/commit/4526be28a9fd863e8d39ad7ebf811ec2978a3023 To be included in the Timestamper 1.4 release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14932) Compact encoding for timestamps, alternative to console note encoding
stevengbrown updated JENKINS-14932 Compact encoding for timestamps, alternative to console note encoding Change By: stevengbrown (01/Oct/12 3:46 AM) Description: 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. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14932) Compact encoding for timestamps, alternative to console note encoding
stevengbrown updated JENKINS-14932 Compact encoding for timestamps, alternative to console note encoding Change By: stevengbrown (29/Sep/12 4:09 PM) Description: 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 increases the file size of the log .- They make file and makes 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. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14932) Compact encoding for timestamps, alternative to console note encoding
stevengbrown updated JENKINS-14932 Compact encoding for timestamps, alternative to console note encoding Change By: stevengbrown (29/Sep/12 3:54 PM) Description: Instead of relying on The Timestamper plugin currently inserts a console notes, store note into every line of the timestamps in a more compact and human-readable format build's log file . The [ console 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 in a separate file to the number of elapsed milliseconds since the build started console, and in a more efficient format . The Timestamper plugin would still need a way to replace insert these timestamps when Jenkins displays back into the console log. This may require changes to when it is being viewed in 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. * The /timestamps URL (introduced in version 1.3.2) must continue to read the console notes when this option has been selected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
