StrictHostKeyChecking=off should be StrictHostKeyChecking=no #455
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This plugin was upgraded on our Jenkins server, and we were unaware of the host key requirement changes (and our AMIs are incompatible without some extra effort). We were unable to continue without downgrading, because the SSH syntax for the "off" option is incorrect, leading to the following error, even when the "Host Key Verification Strategy" was set to off:
It should be
-o StrictHostKeyChecking=no
(we have every intention of fixing the AMIs, and the new feature makes sense, but we like to keep our Jenkins plugins relatively up-to-date, and breaking changes with more restrictive defaults make this difficult)