Page MenuHomePhabricator

Enable ansicolor globally in Jenkins when plugin is released
Closed, ResolvedPublic


The Ansicolor plugin has a feature in master to enable the plugin globally.


When it is released, we should update the plugin on Jenkins instances and enable the plugin globally. Then I guess we can cleanup the JJB configuration to remove ansicolor entirely.

Event Timeline

It looks like the 0.6.3 release is available and contains this commit.

We have ansicolor 0.6.2 right now.

0.6.3 (02/24/2020)

  • #163: Use OpenJDK on Trusty Linux in Travis-CI - @dblock.
  • #163: Cache maven installation in Travis-CI - @dblock.
  • #165: Allow for specifying a global color map - @kcboschert.
  • #168: Fix for working with moving sequences and other invisible escape codes - @tszmytka
  • #169: Set up config and jenkins pipeline for testing/building the plugin on - @tszmytka
  • #171: Display colors without reloading page - @jglick.
hashar triaged this task as Medium priority.Apr 18 2020, 5:51 PM

Mentioned in SAL (#wikimedia-releng) [2020-05-06T13:29:46Z] <hashar> Updating Jenkins ansicolor from 0.6.2 to 0.6.3 # T233688

Mentioned in SAL (#wikimedia-releng) [2020-05-06T13:50:05Z] <hashar> Jenkins: enable xterm ansi color map for all builds via # T233688

I have updated the plugin and set xterm has the color map for all builds. So tentatively we should be able to remove the per jobs configuration we have in jjb:

    - ansicolor

Change 594716 had a related patch set uploaded (by Hashar; owner: Hashar):
[integration/config@master] jjb: remove ansicolor, globally enabled

Mentioned in SAL (#wikimedia-releng) [2020-05-06T20:20:52Z] <hashar> Running jjb for all Jenkins jobs to drop ansicolor definition (now globally enabled) # T233688

Change 594716 merged by jenkins-bot:
[integration/config@master] jjb: remove ansicolor, globally enabled