Fixed in https://github.com/dblock/jenkins-ansicolor-plugin/issues/3.

In versions 0.3.0 and 0.3.1 of ANSI color plugin the strange symbols show up again. Version 0.2.1 is still ok.

This affects us at the moment.

Jenkins ver 1.508
ANSIColor 0.31

It makes our log files 1000x larger - this is ridiculous!

Suggested temporary fix (until JENKINS-13816 allows better way of doing this):

— src/main/java/hudson/plugins/ansicolor/AnsiColorNote.java (revision 36259)
+++ src/main/java/hudson/plugins/ansicolor/AnsiColorNote.java (working copy)
@@ -65,6 +65,7 @@
*/
@Override
public ConsoleAnnotator annotate(Object context, MarkupText text, int charPos) {
+ if (this.data.contains(ConsoleNote.PREAMBLE_STR)) return null;
try {
String colorizedData = colorize(StringEscapeUtils.escapeHtml(this.data), this.getColorMap());
if (! colorizedData.contentEquals(this.data)) {

This also increases the log sizes considerably. 100k -> 16mb

Still true for ansicolor 0.4.1 :/

Yes, these appear to be ~2Kb (7-zip) compressed files embedded in each line of output. This has to be one of the most egregious examples of 'bloat' which I have seen. I would love to hear an explanation of why this was ever thought to be a good idea.

I updated the prio on this to major because nodejs projects tend to have MASSIVE logs when this is enabled.

Is there any movement on this? Could the ansi information be stored some other way? Or re-calculated on the fly when displayed?

Ansicolor 0.6.0 was just released with a fix for this issue.