+1 same here, disabling resolved the issue of configuration, but now jobs can publish over ssh..

Some more info:
This happens because the checkUrl in the execCommand textarea is not escaped with '
This textarea is defined in textarea.jelly in the publish-over plugin

I've send a pull request ( https://github.com/jenkinsci/publish-over-plugin/pull/3 ) but I'm unsure if it's the right way to fix the issue. It does make everything usuable again. And the checkUrl is properly escaped when using publish-over-ssh.
I'd like someone to validate the fix.

^^ Pull request does not properly fix issue. The warning that one of sourceFiles or execCommand has to be populated is always shown. The fix is a workaround though. You can edit the job config again and just ignore the warning. And the publish-over-ssh works. ( To apply temporarily fix. Replace the publish-over artifact from the plugins WEB-INF/lib/ folder with the patched one )

This issue might be the same that makes, JENKINS-19389 happen.

I have been unable to replicate this issue, can someone provide additional information?

For your information, all publish-over-ssh component type JENKINS issues related to the Publish Over SSH plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues

Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues/191
And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-ssh-plugin/issues?q=%22JENKINS-19279%22

(Note: this is an automated bulk comment)