Only if maintainer wants to keep it ;)
On Thursday, October 22, 2015 at 6:46:55 PM UTC+3, Jesse Glick wrote:
>
> On Wed, Oct 21, 2015 at 1:38 PM, Owen Mehegan > wrote:
> > Turns out this was a failure of the plugin to migrate its global
> > configuration after some code was refactored. Open to
On Wed, Oct 21, 2015 at 1:38 PM, Owen Mehegan 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
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 o
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
