Looking for some help with a baffling plugin bug (ansicolor)

[Owen Mehegan]

Myself and the maintainers of the jenkins-ansicolor plugin have been struggling with a weird bug. So far I am the only one who can reproduce it, and I can only repro it on my production Jenkins server. A seemingly-identical test server does not exhibit the bug. We seem to have exhausted most of the obvious possible causes. I have isolated the breakage to a specific commit, but that hasn't helped us come up with a fix. I'm hoping that getting some additional experienced eyes on the problem might generate some other suggestions for how we could debug this (I'm also personally limited in that I don't really know Java at all). My comment at https://github.com/dblock/jenkins-ansicolor-plugin/issues/57#issuecomment-148869752 summarizes the current state of the bug.

Thanks in advance to anyone who takes a look :) 

[Owen Mehegan]

Turns out this was a failure of the plugin to migrate its global configuration after some code was refactored. Open to any guidance about best practices for doing that cleanly during an upgrade.

[Jesse Glick]

On Wed, Oct 21, 2015 at 1:38 PM, Owen Mehegan <ow...@nerdnetworks.org> wrote:
> Turns out this was a failure of the plugin to migrate its global
> configuration after some code was refactored. Open to any guidance about
> best practices for doing that cleanly during an upgrade.

https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility

[Kanstantsin Shautsou]

Only if maintainer wants to keep it ;)