You can bisect by Jenkins version number; or just check if 2.60 & 2.61
work but 2.62 does not, implying that JENKINS-44120 is at fault.

And of course we would want to improve

https://github.com/jenkinsci/acceptance-test-harness/blob/786be14d7096e2d1464e6dd41e9e003a3e20906f/src/test/java/plugins/SshSlavesPluginTest.java#L75-L81

to reproduce the issue, perhaps by creating variants of

https://github.com/jenkinsci/docker-fixtures/tree/fe4f33921a290c352ad757a896bd570856ae062c/src/main/resources/org/jenkinsci/test/acceptance/docker/fixtures/SshdContainer

that use different key formats (or whatever the problem turns out to be).

-- 
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/CANfRfr3YkkfUbSW6CRt0N_JYJDw9xmWEvsp10AHJnJ0k6kP9_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to