Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-55139

ansicolor 0.6.0 shows terminal escape sequences in console log

    Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: ansicolor-plugin
    • 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
    • Similar Issues:
    • Released As:
      ansicolor 0.6.2

      Description

      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:
      ok: [essf0desc]

      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.

        Attachments

          Activity

          Hide
          kugel Thomas M added a comment -

          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.

          Show
          kugel Thomas M added a comment - 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.
          Hide
          dhoer Dennis Hoer added a comment - - edited

          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 
                       """ 
                     }
                   }
                   ...
                 }
               }
          
          Show
          dhoer Dennis Hoer added a comment - - edited 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 """ } } ... } }
          Hide
          initialzero Marc Benstein added a comment -

          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:

          Show
          initialzero Marc Benstein added a comment - 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:
          Hide
          prifiz Valentin Baranov added a comment -

          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?

          Show
          prifiz Valentin Baranov added a comment - 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?
          Hide
          vmeghani88 Vishal Meghani added a comment - - edited

          I am also seeing the same issue with 0.6.2 version of plugin and CloudBees Jenkins Enterprise 2.164.3.2-rolling.

          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***************************************************************************** STAGE INIT *****************************************************************************

           

          Show
          vmeghani88 Vishal Meghani added a comment - - edited I am also seeing the same issue with 0.6.2 version of plugin and CloudBees Jenkins Enterprise 2.164.3.2-rolling. 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***************************************************************************** STAGE INIT *****************************************************************************  

            People

            • Assignee:
              dnusbaum Devin Nusbaum
              Reporter:
              cloos Christian Loos
            • Votes:
              12 Vote for this issue
              Watchers:
              28 Start watching this issue

              Dates

              • Created:
                Updated: