Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
Jenkins version: 2.138.2
JDK: java-1.8.0-openjdk-1.8.0.161-2.b14.el7.x86_64
OS: CentOS 7 64 bit
Pipeline plugin version: 2.6
Jenkins is running directly using SSH agents for the slaves. The slaves are all running CentOS 7 with some of those agents being containers. Jenkins is access through a smart proxy and I'm running the latest version of Google Chrome.Jenkins version: 2.138.2 JDK: java-1.8.0-openjdk-1.8.0.161-2.b14.el7.x86_64 OS: CentOS 7 64 bit Pipeline plugin version: 2.6 Jenkins is running directly using SSH agents for the slaves. The slaves are all running CentOS 7 with some of those agents being containers. Jenkins is access through a smart proxy and I'm running the latest version of Google Chrome.
Description
Pipeline:
node('master'){ ansiColor('xterm') { sh 'echo -e "\033[31mRed\033[0m"' } wrap([$class: 'AnsiColorBuildWrapper', 'colorMapName': 'XTerm']) { sh 'echo -e "\033[31mRed\033[0m"' } } node('ansible'){ ansiColor('xterm') { sh 'echo -e "\033[31mRed\033[0m"' } wrap([$class: 'AnsiColorBuildWrapper', 'colorMapName': 'XTerm']) { sh 'echo -e "\033[31mRed\033[0m"' } }
Output:
I've verified I see ANSI coloring on a freestyle project restricted to the same 'ansible' label
Shell build step
echo -e "\033[31mRed\033[0m"
Output
I've verified this happens on multiple Jenkins instances running 2.138.2. This started happening after the following plugin updates:
-rw-r--r--. 1 jenkins jenkins 560808 Oct 12 16:54 workflow-cps.jpi -rw-r--r--. 1 jenkins jenkins 111622 Oct 12 16:54 workflow-job.jpi -rw-r--r--. 1 jenkins jenkins 311324 Oct 12 16:54 ws-cleanup.jpi -rw-r--r--. 1 jenkins jenkins 360909 Oct 12 16:54 workflow-support.jpi
Attachments
Issue Links
- relates to
-
-
- Resolved
-
-
-
- Resolved
-
-
JENKINS-38381 [JEP-210] Optimize log handling in Pipeline and Durable Task
-
- Resolved
-
- links to
Activity
Thus the fixes for ant and pipeline-maven have been released; as well as the hotfix of this issue as originally filed for ansicolor (PRs 128 & 130), though the full fix through rewrite (PR 132) which is merged but not yet released by dnusbaum (and which also requires a post-LTS version of Jenkins core).
jglick I just released the full fix for ansicolor in version 0.6.0 of the plugin.
I have reproduced the issue with Jenkins 2.332.1 and AnsiColor 1.0.1. The nodes are started with bash and they are using WebSocket connection if that matters. The node executes jar-file which prints color coded messages in log. Everything is fine on master, but no colors or color escape sequences in the output for nodes.
Jenkins version: 2.332.1
JDK: openjdk-11+28
OS: Oracle Linux Server 7.9
Konstantin Berndikov
added a comment - - edited I have reproduced the issue with Jenkins 2.332.1 and AnsiColor 1.0.1. The nodes are started with bash and they are using WebSocket connection if that matters. The node executes jar-file which prints color coded messages in log. Everything is fine on master, but no colors or color escape sequences in the output for nodes.
Jenkins version: 2.332.1
JDK: openjdk-11+28
OS: Oracle Linux Server 7.9 toisen best to file a fresh issue linked to this one with steps to reproduce from scratch.
Delivered in pipeline-maven-plugin 3.6.0