When run using the default http protocol, if the Jenkins CLI finds there is an SSH key in the user's home directory which requires a passcode, it will prompt for that passcode. It should not be doing this.
- blocks
-
JENKINS-41745 Remoting-free CLI
-
- Resolved
-
Seems to have always been true: happens even in older versions of Jenkins when using, say, --password. Just more noticeable now.
Workaround is to explicitly pass -noKeyAuth if you know you have a private key in the default location (~/.ssh/id_[rd]sa) with a passphrase.