On Fri, Aug 19, 2011 at 12:40 AM, Andrew Bayer <[email protected]> wrote: > In my experience, this tends to clear up after killing/restarting the > offending slave, but I'm not sure what the underlying problem in Jenkins > actually is.
After the last upgrade of Jenkins, we've seen quite a few problems with incompatible classes, despite most of our slaves being restarted all the time since we take them offline when idle. I'll see if I can force an update by removing the slave jars. /niklas
