[JIRA] (JENKINS-36886) Terminal escape sequences being shown
Title: Message Title Jon Hermansen assigned an issue to Jon Hermansen Jenkins / JENKINS-36886 Terminal escape sequences being shown Change By: Jon Hermansen Assignee: Nicolas De Loof Jon Hermansen Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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/d/optout.
[JIRA] (JENKINS-36886) Terminal escape sequences being shown
Title: Message Title John Mellor commented on JENKINS-36886 Re: Terminal escape sequences being shown A specific problem resulting from this more generic issue Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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/d/optout.
[JIRA] (JENKINS-36886) Terminal escape sequences being shown
Title: Message Title John Mellor created an issue Jenkins / JENKINS-36886 Terminal escape sequences being shown Issue Type: Bug Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 2016/Jul/22 7:29 PM Environment: Ubuntu Linux, Jenkins 1.656, output from Robot, pip, many others. Labels: regression user-experience plugins Priority: Minor Reporter: John Mellor ANSI escape sequences in jobs run directly on a Jenkins slave are either not present or stripped out. These escape sequences are not stripped when running in a docker image being managed by this plugin. This makes dockerized build output parsing different, and unxexpectedly tricky for postbuild actions, and in many cases makes the output much noisier than necessary. e.g: a job that does a simple "ls --color=auto" can be easily shown in a docker machine to have color escapes present in the log, but not present in a non-docker build. Doing the same action on a docker image and on a real machine, we can see that the output in colorized in both cases, narrowing the issue down to a problem in the Jenkins plugin.
