Sounds like a solid plan to me. +1
On Sat, Aug 16, 2014 at 7:29 AM, Alex Harui <aha...@adobe.com> wrote: > In fact, the slave is listed as off-line right now and no jobs are running > and that's what is supposedly fixed in newer versions. > > On 8/16/14 3:04 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: > > >The version you are talking about is the Jenkins version? Has anything > >been fixed in the last version that could be related? I would assume the > >problems we are having are not related directly to the jenkins verion, > >but I might be wrong ;-) > > > >Chris > > > > > >-----Ursprüngliche Nachricht----- > >Von: Alex Harui [mailto:aha...@adobe.com] > >Gesendet: Samstag, 16. August 2014 07:37 > >An: dev@flex.apache.org > >Betreff: [Jenkins] upgrade mustella server to 1.563? > > > >This post: > > > http://jenkins-ci.361315.n4.nabble.com/JIRA-core-JENKINS-22758-Jenkins-gt- > >1 > >-560-breaks-Jenkins-slave-handling-NIO-JNLP-related-using-swarm--td4699957 > >. > >html > > > >seems to related to the problem with the mustella server where it starts > >to fail with the stack below. Any objections to trying an upgrade to > >1.563 (mustella server is currently at 1.562)? > > > >-Alex > > > >FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: > >Failed to abort > >hudson.remoting.RequestAbortedException: > >hudson.remoting.RequestAbortedException: java.io.IOException: Failed to > >abort ... > > > >
