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.

          [JENKINS-36886] Terminal escape sequences being shown

          John Mellor added a comment -

          A specific problem resulting from this more generic issue

          John Mellor added a comment - A specific problem resulting from this more generic issue

            jonhermansen Jon Hermansen
            alt_jmellor John Mellor
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: