Whenever the CLI tries to to connect to the Jenkins server, it offers the before mentioned SSH keys. When the user has those keys but dondoesn't want to use them to authenticate, preventing being prompted by the key's password, it's possible to use the
-noKeyAuth argument to skip being prompted for the key's password. This way the CLI will never try to use the SSH available SSH keys available.
1.419 and later
If your Jenkins requires authentication, you should set up public key authentication. Login from the web UI and go to
//yourserver.com/me/configure, then set your public keys in the designated text area. When connecting to the server, the CLI will look for
~/.ssh/id_rsa and use those to authenticate itself against the server. Alternatively, the
-i option can be used to explicitly specify the location of the private key.