-
Bug
-
Resolution: Fixed
-
Major
-
None
Since Hudson 1.349, console notes can be embedded into the console output file. These notes are stored in an encoded format and are intended to be stripped out before the console is displayed.
The Log Parser Plugin, since it reads from the console output file directly, puts these encoded notes into the Parsed Console Output page. Here is an example:
[8mha:AAAAdB+LCAAAAAAAAABb85aBtbiIQSOjNKU4P0+vIKc0PTOvWK8kMze1uCQxtyC1SC8ExvbLL0llgABGJgZGLwaB3MycnMzi4My85FTXgvzkjIoiBimoScn5ecX5Oal6zhAaVS9DRQGQ1prw898HAAlKmbGBAAAA [0m
The attached patch JENKINS-7263.patch strips out these console notes.
[JENKINS-7263] Encoded console notes appear in the Parsed Console Output
ssplett
added a comment - The problem does not occur since a long time. If it occurs again, I will reopen this issue. Sorry for all trouble this issue might have caused so far.
ssplett
added a comment - The problem does not occur since a long time. If it occurs again, I will reopen this issue. Sorry for all trouble this issue might have caused so far. ssplett
added a comment - Sorry... Closed wrong issue... 
jborghi
added a comment - Strip ConsoleNote during both parsing and display. ConsoleNote(s) may be turned on/off by individual plugin and/or project. These notes will interfere with patterns depending on where they are injected, and how the regexp patterns are anchored, so stripping seemed the cleanest approach.
jborghi
added a comment - Strip ConsoleNote during both parsing and display. ConsoleNote(s) may be turned on/off by individual plugin and/or project. These notes will interfere with patterns depending on where they are injected, and how the regexp patterns are anchored, so stripping seemed the cleanest approach. 
Rinat, if you are happy for me to commit and release this change, please assign back to me. I could also perform some code cleanup, such as removing unused code, making use of generics, and replacing StringBuffer usages with StringBuilder.