There will be two new options in the Build Environment section of the job configuration
From the Jenkins home page, click "Manage Jenkins" and then click on "Configure System"
Find the SSH section (as below)
This configures the default key that will be used by all of the SSH configurations.
If the key is encrypted with a passphrase then set it here.
The location, on the Jenkins master, of the private SSH key to use.
Paste the private key into this box.
This option will remove the ability to execute commands from this plugin.
Click on the "Add" button next to "SSH Servers"
Fill in Name, Hostname, Username and Remote Directory. see Publish Over ... for common options for Host Configurations
The user that will be used to connect to the host.
Selecting this option will produce 3 more configuration boxes that mirror the options available for the Jenkins SSH Key.
If either Path to key or Key are configured then this is the passphrase to use with the encrypted key.
This option will remove the ability to execute commands using this configuration.
Ensure that the public key (counterpart to the private key configured above) is in the authorized keys file for the user that you connect as on the server you want to connect to.
This plugin includes a builder which enables the use of the publisher during the build process.
This means that you can send newly created packages to a remote server and install them, start and stop services that the build may depend on and many other use cases.
If there is anything in this configuration box then it will be executed on the remote server.
Configure a timeout for the Exec command to use.
Run the Exec command in a pseudo TTY.
If you click the "Advanced..." button that is immediately below the "Add Server" button, you will make more configuration options available.
If you are configuring an action in a promotion, new options will become available.
Skip to end of metadata Go to start of metadata