[JIRA] (JENKINS-55139) ansicolor 0.6.0 shows terminal escape sequences in console log

[cloos@netsandbox.de (JIRA)]

Christian Loos created an issue

Jenkins / JENKINS-55139 ansicolor 0.6.0 shows terminal escape sequences in console log Issue Type: Bug Assignee: Unassigned Components: ansicolor-plugin Created: 2018-12-12 09:05 Environment: Jenkins version: 2.150.1 JDK: OpenJDK Runtime Environment 1.8.0_191-8u191-b12-0ubuntu0.16.04.1-b12 OS: Ubuntu 16.04.5 LTS ansicolor 0.6.0 timestamper 1.8.10 Labels: plugin consoleoutput regression Priority: Major Reporter: Christian Loos Since I updated the ansicolor plugin to 0.6.0, I see escape sequences in the terminal log (the log is from an ansible-playbook run): consoleText in WebUI: [0;32mok: [essf0desc] [0m log file: [[0;32mok: [essf0desc][[0m When i downgrade the ansicolor plugin to 0.5.3, I don't see the escape sequences in the log: consoleText in WebUI: ok: [essf0desc] log file: [[8mha:////4GByXBh6D5sO4uIaL/Xvo6rBHYkdqIOcMtgU7KVDnLnuAAAApR+LCAAAAAAAAP9b85aBtbiIQT2jNKU4P0+vIKc0PTOvWC8xrzgzOT8nv0gvODO3ICfVoyQ3xy+/JNU2Yj/Tagmf50wMjD4M7CWJ6SCJEgYhn6zEskT9nMS8dP3gkqLMvHTriiIGKaihyfl5xfk5qXrOEBpkDgMEMDIxMFQUlDDI2RQXJOYpFJdU5qTaKoEttlJQNjBwdjEwsFayAwAsE8VZpQAAAA==[[0mok: [essf0desc][[8mha:////4MLkG6V+s9c4kbbINbBZTN8IdUcULVaJJVRaElSmS5VEAAAAkR+LCAAAAAAAAP9b85aBtbiIQT2jNKU4P0+vIKc0PTOvWC8xrzgzOT8nv0gvODO3ICfVoyQ3xy+/JNU2Yj/Tagmf50wMjD4M7CWJ6SCJEgYhn6zEskT9nMS8dP3gkqLMvHTriiIGKaihyfl5xfk5qXrOEBpkDgMEMDIxMFQUlDCw2+gXFyTm2QEAI9P8iI4AAAA=[[0m The log output let me assume that the changes in 0.6.0 maybe interference with the timestamper plugin. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum updated an issue

Jenkins / JENKINS-55139 ansicolor 0.6.0 shows terminal escape sequences in console log

Change By: Devin Nusbaum Attachment: ansicolor.hpi

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log There is some additional discussion on https://github.com/jenkinsci/ansicolor-plugin/issues/145. I am not sure exactly what the issue is with ansible, but it looks like at least TerraForm is using multiline input, which I think should be fixed by https://github.com/jenkinsci/ansicolor-plugin/pull/137 (merged but not released). If anyone seeing the issue can test out the attached SNAPSHOT build of the plugin based on the current master (ansicolor.hpi) and report on whether that fixes the issue, makes things better, makes things worse, or makes no difference, that would be very helpful. ansicolor.hpi

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum edited a comment on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

There is some additional discussion on [https://github.com/jenkinsci/ansicolor-plugin/issues/145.] I am not sure exactly what the issue is with ansible, but it looks like at least TerraForm Terraform is using multiline input, which I think should be fixed by [https://github.com/jenkinsci/ansicolor-plugin/pull/137] (merged but not released). If anyone seeing the issue can test out the attached SNAPSHOT build of the plugin based on the current master ([^ansicolor.hpi]) and report on whether that fixes the issue, makes things better, makes things worse, or makes no difference, that would be very helpful. [^ansicolor.hpi]

Add Comment

[vektory79@gmail.com (JIRA)]

Victor Verbitsky commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

I tried this snapshot and it's makes no difference...

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

Thanks for trying it out Victor Verbitsky! It would be great if anyone seeing the issue could report whether they are seeing variant 1 or 2 of the issue while ansicolor 0.6.x is installed as described in my comment on the GitHub issue.

Add Comment

[vektory79@gmail.com (JIRA)]

Victor Verbitsky commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

If ansicolor 0.6.x is installed then I see the 1 variant of the issue.

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

Are there any error messages in your logs? Do you see any kind of coloration in any jobs? What tools are producing colorized output in your logs (Ansible)? Can you copy-paste one of the lines that is showing up incorrectly here (preferably replacing literal occurrences of the character 0x1B with 0x1B here so we can see how control characters are being processed?)

Add Comment

[vektory79@gmail.com (JIRA)]

Victor Verbitsky commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

> Are there any error messages in your logs?

I haven't found any meaningful messages.

> Do you see any kind of coloration in any jobs?

No at all.

> What tools are producing colorized output in your logs (Ansible)?

Apache Maven 3.6.0 (with special flags to force the coloration).

> Can you copy-paste one of the lines that is showing up incorrectly here

{{[ [1;33mWARNING [m] }} {{[ [1;33mWARNING [m] It is highly recommended to fix these problems because they threaten the stability of your build.}} {{[ [1;33mWARNING [m] }} {{[ [1;33mWARNING [m] For this reason, future Maven versions might no longer support building such malformed projects.}} {{[ [1;33mWARNING [m] }} {{[ [1;34mINFO [m] [1m------------------------------------------------------------------------ [m}} {{[ [1;34mINFO [m] [1mReactor Build Order: [m}} {{[ [1;34mINFO [m] }} {{[ [1;34mINFO [m] ru.krista:root:pom [pom]}} {{[ [1;34mINFO [m] ru.krista:core:pom [pom]}} {{[ [1;34mINFO [m] ru.krista.core:common:pom [pom]}} {{[ [1;34mINFO [m] ru.krista.core.common:utils:jar [takari-jar]}} {{[ [1;34mINFO [m] ru.krista.core:ioc:pom [pom]}}

> preferably replacing literal occurrences of the character 0x1B with 0x1B here so we can see how control characters are being processed?

Sorry, but I don't know how to do this... I just see this log instead of color text. With 0.5.3 all colors is in place here.

Add Comment

[vektory79@gmail.com (JIRA)]

Victor Verbitsky edited a comment on JENKINS-55139

[vektory79@gmail.com (JIRA)]

Victor Verbitsky commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

> preferably replacing literal occurrences of the character 0x1B with 0x1B here so we can see how control characters are being processed? Sorry twice! I found them! [0x1B[1;33mWARNING0x1B[m] [0x1B[1;33mWARNING0x1B[m] It is highly recommended to fix these problems because they threaten the stability of your build. [0x1B[1;33mWARNING0x1B[m] [0x1B[1;33mWARNING0x1B[m] For this reason, future Maven versions might no longer support building such malformed projects. [0x1B[1;33mWARNING0x1B[m] [0x1B[1;34mINFO0x1B[m] 0x1B[1m------------------------------------------------------------------------0x1B[m [0x1B[1;34mINFO0x1B[m] 0x1B[1mReactor Build Order:0x1B[m [0x1B[1;34mINFO0x1B[m] [0x1B[1;34mINFO0x1B[m] ru.krista:root:pom [pom] [0x1B[1;34mINFO0x1B[m] ru.krista:core:pom [pom] [0x1B[1;34mINFO0x1B[m] ru.krista.core:common:pom [pom] [0x1B[1;34mINFO0x1B[m] ru.krista.core.common:utils:jar [takari-jar] [0x1B[1;34mINFO0x1B[m] ru.krista.core:ioc:pom [pom]

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

Victor Verbitsky Maven coloring is explicitly validated in this test case. Are you sure that you are seeing that output for a build while you are still running Ansicolor 0.6.0? If you have Ansicolor 0.5.3 installed, then the logs are expected to look like that for builds that originally ran while Ansicolor 0.6.0 was installed. I am not able to reproduce your issue on Ansicolor 0.6.0. If you are able to create a similar test case to the Maven one I linked that demonstrates the issue you are seeing, that would be very helpful.

Add Comment

[jonas.d.lindstrom@netent.com (JIRA)]

Jonas Lindström commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

Fairly minimal test case: docker run -p 8080:8080 -p 50000:50000 jenkins/jenkins:2.150.2 Don't install any plugins Go to Plugin Manager, install AnsiColor 0.5.3 from https://updates.jenkins.io/download/plugins/ansicolor/ Create a free-style job with "Color ANSI Console Output", and a build step "Execute shell" containing: echo "\e[1m\e[34mbold blue text\e[0m\e[0m" Build the job. Output bold blue text Go to Plugin Manager, upgrade AnsiColor to 0.6.1 and restart Jenkins Build the job. Output: bold blue text [0m

Add Comment

[jonas.d.lindstrom@netent.com (JIRA)]

Jonas Lindström edited a comment on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

Fairly minimal test case: * {{docker run -p 8080:8080 -p 50000:50000 jenkins/jenkins:2.150.2}} * Go to http://localhost:8080 * Don't install any plugins * Go to Plugin Manager, install AnsiColor 0.5.3 from [https://updates.jenkins.io/download/plugins/ansicolor/] * Create a free-style job with "Color ANSI Console Output", and a build step "Execute shell" containing: {{echo "\e[1m\e[34mbold blue text\e[0m\e[0m"}} * Build the job. Output *{color:#4c9aff}bold blue text{color}* * Go to Plugin Manager, upgrade AnsiColor to 0.6.1 and restart Jenkins * Build the job. Output: {color:#4c9aff}*bold blue text*{color} [0m

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

Jonas Lindström Thanks for the reproduction case. I think it would be handled by [PR 147https://github.com/jenkinsci/ansicolor-plugin/pull/147], which is ready to be merged and released, although I'm not sure when I'll have time to release the plugin.

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum edited a comment on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

[~jl68] Thanks for the reproduction case. I think it would be handled by [PR 147https 147|https ://github.com/jenkinsci/ansicolor-plugin/pull/147], which is ready to be merged and released, although I'm not sure when I'll have time to release the plugin.

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum assigned an issue to Devin Nusbaum

Jenkins / JENKINS-55139

ansicolor 0.6.0 shows terminal escape sequences in console log

Change By: Devin Nusbaum Assignee: Devin Nusbaum

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum updated JENKINS-55139

Jenkins / JENKINS-55139 ansicolor 0.6.0 shows terminal escape sequences in console log

Change By: Devin Nusbaum Status: In Progress Review

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum started work on JENKINS-55139

Change By: Devin Nusbaum Status: Open In Progress

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log I just released 0.6.2 with a change that should fix this issue for the cases I am aware of. If you are still seeing it after the upgrade, please copy-and-paste some of the broken output from Jenkins here (preferably replacing literal occurrences of the ASCII character 0x1b with the text 0x1b so we can see what is happening to the escape sequences).

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum updated JENKINS-55139

Jenkins / JENKINS-55139

ansicolor 0.6.0 shows terminal escape sequences in console log

Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: ansicolor 0.6.2

Add Comment

[jonas.d.lindstrom@netent.com (JIRA)]

Jonas Lindström commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log As far I can see, it looks good now. Thanks for the fix!

Add Comment

[cloos@netsandbox.de (JIRA)]

Christian Loos commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

Sorry for the delay. I had today time to test it again. And I still can see the control charcters. After updating to 0.6.2, control character in /console and /consoleText: [[0;32mok: [lxsrvmgi1360][[0m After downgrading to 0.5.3, no control character in /console and /consoleText: [[8mha:////4GByXBh6D5sO4uIaL/Xvo6rBHYkdqIOcMtgU7KVDnLnuAAAApR+LCAAAAAAAAP9b85aBtbiIQT2jNKU4P0+vIKc0PTOvWC8xrzgzOT8nv0gvODO3ICfVoyQ3xy+/JNU2Yj/Tagmf50wMjD4M7CWJ6SCJEgYhn6zEskT9nMS8dP3gkqLMvHTriiIGKaihyfl5xfk5qXrOEBpkDgMEMDIxMFQUlDDI2RQXJOYpFJdU5qTaKoEttlJQNjBwdjEwsFayAwAsE8VZpQAAAA==[[0mok: [lxsrvmgi1360][[8mha:////4MLkG6V+s9c4kbbINbBZTN8IdUcULVaJJVRaElSmS5VEAAAAkR+LCAAAAAAAAP9b85aBtbiIQT2jNKU4P0+vIKc0PTOvWC8xrzgzOT8nv0gvODO3ICfVoyQ3xy+/JNU2Yj/Tagmf50wMjD4M7CWJ6SCJEgYhn6zEskT9nMS8dP3gkqLMvHTriiIGKaihyfl5xfk5qXrOEBpkDgMEMDIxMFQUlDCw2+gXFyTm2QEAI9P8iI4AAAA=[[0m

Add Comment

[cloos@netsandbox.de (JIRA)]

Christian Loos reopened an issue

Jenkins / JENKINS-55139

ansicolor 0.6.0 shows terminal escape sequences in console log

Change By: Christian Loos Resolution: Fixed Status: Resolved Reopened

Add Comment

[robinverduijn.github@gmail.com (JIRA)]

Robin Verduijn commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log Note that for me, I am also still seeing the control characters in the console output but only while watching an active build. Inspecting the console output after a build has completed does render them correctly.

Add Comment

[david.aldrich@emea.nec.com (JIRA)]

David Aldrich commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

I am seeing the same behaviour as Robin Verduijn.

Add Comment

[anthony@pioli.com (JIRA)]

Anthony Pioli commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

I'm seeing the same behavior as Robin Verduijn as well

Add Comment

[vmeghani@salesforce.com (JIRA)]

Vishal Meghani commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

I am also seeing the same issue with 0.6.2 version of plugin and CloudBees Jenkins Enterprise 2.164.3.2-rolling. Interestingly it was not there for Jenkins-2.150.3.2-1 with 0.6.2 version on ansi color plugin.  After refreshing the page colors appear. Issue only happens when you have opened console output before the {{ansiColor }}option is executed. However, downgrading to 0.5.3, resolves the issue. Devin Nusbaum eg. [1;37;45m***************************************************************************** [0m [1;37;45mSTAGE INIT [0m [1;37;45m***************************************************************************** [0m

Add Comment

[vmeghani@salesforce.com (JIRA)]

Vishal Meghani edited a comment on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

I am also seeing the same issue with 0.6.2 version of plugin and CloudBees Jenkins Enterprise 2.164.3.2-rolling. Interestingly it was not there for Jenkins-2.150.3.2-1 with 0.6.2 version on ansi color plugin.  After refreshing the page colors appear. Issue only happens when you have opened console output before the  \

{{ansiColor }}option is executed.

However, downgrading to 0.5.3, resolves the issue.

[~dnusbaum] eg.

[1;37;45m***************************************************************************** [0m [1;37;45mSTAGE INIT [0m [1;37;45m***************************************************************************** [0m

Add Comment

[valentin.baranov@netcracker.com (JIRA)]

Valentin Baranov commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

Tried to downgrade to 0.5.3 - it didn't help. It is reproduced only on Maven Projects. Only checking "Color ANSI output" workarounds this but it's color schemes don't suite for us and there're lots of jobs to reconfigure. Can anybody please help with this issue?

Add Comment

[initialzero@gmail.com (JIRA)]

Marc Benstein updated an issue

Jenkins / JENKINS-55139

ansicolor 0.6.0 shows terminal escape sequences in console log

Change By: Marc Benstein Attachment: image-2019-08-21-16-31-39-960.png

Add Comment

[initialzero@gmail.com (JIRA)]

Marc Benstein commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log This seems similar to my issue with v0.6.2. This was working in v0.5.x I have a freestyle project where I have enabled ansi color with xterm. A single shell command with: echo "testing-1.2.300" | grep -E --color=always '[0-9]+.[0-9]+.[0-9]+' Results in:

Add Comment

[dennis.hoer@gmail.com (JIRA)]

Dennis Hoer commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

I had the same issue with Jenkinsfile and ansible. The problem was I was using single quotes for multiline shell command, e.g., sh ''' . .venv/bin/activate molecule test ''' Switching to double quotes fixed the issue, e.g., pipeline { ... options { ansiColor('xterm') ... } stages { ... stage('Test') { steps { sh """ . .venv/bin/activate molecule test """ } } ... } }

Add Comment

[dennis.hoer@gmail.com (JIRA)]

Dennis Hoer edited a comment on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

I had the same issue with Jenkinsfile and ansible. The problem was I was using single quotes for multiline shell command, e.g.,

{code:java}

sh '''       . .venv/bin/activate       molecule test      '''

{code}

Switching to double quotes fixed the issue, e.g.,

{code:java}

pipeline {        ...        options {          ansiColor('xterm')          ...       }

stages {          ...          stage('Test') {            steps {              sh """                 . .venv/bin/activate                 molecule test              """            }         }         ...        }      }

{code}

Add Comment

[thomas.martitz@mailbox.org (JIRA)]

Thomas M commented on JENKINS-55139

Re: ansicolor 0.6.0 shows terminal escape sequences in console log

I can confirm this bug and also that downgrading to 0.5.3 (from http://updates.jenkins-ci.org/download/plugins/ansicolor/) helps.   My sh commands use double quotes (but only single-line, as in sh "bash path/to/script ${arg1} ${arg2}") already so I cannot confirm Dennis Hoer workaround. With the 0.6.2 I get output similar to Marc Benstein comment.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)