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.
On Monday, October 19, 2015 at 1:59:04 PM UTC-7, Owen Mehegan wrote: > > 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 :) > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/27c20efe-674f-47d3-9096-1fef1a749eff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
