ansicolor-plugin: Colors are not displayed immediately after upgrading to 0.6.0
Test environment
- Jenkins Version: 2.151
- AnsiColor Version: 0.6.0
- Hostsystem: Linux
Expected behavior
When a pipeline build is triggered, if I immediately open the logs as soon as I trigger Build Now
, the colors for that build won’t appear while I am tailing the logs on Jenkins.
If I press back on the browser, open the same build logs again, the logs appear in colors.
I am using a declarative pipeline and using ansiColor('xterm')
inside options
.
Actual behavior
The colors should appear always. Reverting the plugin to 0.5.3 fixes the issue.
Steps to reproduce the behavior
Create a pipeline with ansiColor('xterm')
inside options
.
Press build now and go fast to Console output. I believe you need to get there before the ansiColor
option is executed.
The logs won’t display colors anymore. It will display again if you go back and open logs a second time.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 28
- Comments: 29 (7 by maintainers)
I have current latest Jenkins LTS 2.150.3 with AnsiColor 0.6.2 and I also observe same behavior as @kapoorlakshya . Before refresh I see control characters and no colors. After refresh the colors are displayed properly, no garbage control character. In classic console output. Preferred classic console to the new blue ocean so did not even install the blue ocean.
I have to confirm this issue: refreshing the console log (in classic UI) e.g. via pressing F5 is necessary.
I have same problem Jenkins 2.222.4 ansiColor 0.7.0
Hi, I am also experiencing this when using Cucumber and plugin version 0.6.2 (latest). I see the control characters and no colors in the console output as the text shows up. However, when I refresh the page the control characters disappear and the text shows up in color.
This behavior is not experienced in v0.5.3. Also, this only happens in the classic console output and not in the Blue Ocean view.
Before refresh:
After page refresh:
Raw output:
Pipeline code:
From my POV it would be a better approach to mark #193 as a duplicate and leave #136 open since here you have a lot of participants who loose track otherwise.
Waiting for your fix @e-moshaya!
I just released 0.6.3, notably including #171, which should fix this issue, and #168 (should fix #151 and maybe some other issues that were lacking enough info to reproduce).
I used to have version 0.5.2 and worked flawlessly. Any workaround?
I’m experiencing the same behavior with the plugin. I regularly need to refresh the page for the colors to appear.