On 04/17/2013 12:52 PM, Stephen Connolly wrote:
From my analysis of the code paths the issue is in both 0.23 and 0.24. But if you think otherwise I would be happy to re-review
Yes, the change in 0.24 allowed us to see this issue, which was previously masked. I think this is the root cause of JENKINS-17366.
We need to use 0.22 (the version before ssh-credentials plugin dependency) or 0.25 (which contains the fix.)
On 17 April 2013 19:37, Vojtech Juranek <[email protected] <mailto:[email protected]>> wrote: On Wednesday 17 April 2013 12:08:12 Stephen Connolly wrote: > May want to upgrade to ssh-slaves 0.25 to get the fix for > https://issues.jenkins-ci.org/browse/JENKINS-17648 as that problem could be > nasty in the wild if I understand this issue correctly, it's issue introduced in ssh-slaves 0.24. As 1.509 uses ssh-slaves 0.23, IMHO no upgrade is need, right? -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
-- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
