![]() May be useful for those with exciting network configurations / administrators. By selecting this option, the connection will be initiated from the Jenkins master. Always send from masterīy default, the publisher will connect from the host that has the files that need to be transferred - if a build is performed on a slave, then the transfer would be initiated from the slave. This option is especially useful in the case of a promotion where the main action is to Publish Over. ![]() Setting this option will cause a failure in the publisher to set the build result to FAILED. Fail the build if an error occursīy default, when an error occurs, the publisher will set the build result to UNSTABLE. Set this option to cause the publisher to try to publish to other servers after publishing to a previous configuration has failed. Advanced options Publish to other servers if an error occursīy default, when an error occurs during publishing the publisher will fail and return immediately. All of the publisher options are only exposed when you click on the "Advanced" button (at the bottom of the configuration for this plugin). There are some options that are set at the publisher level - options that affect all of the server connections within. The connect timeout can be configured (in milliseconds) The port that the Server is runnning on can be changed if the server that you are connecting to is not running on the default port for the service that the plugin talks to. A job that uses this configuration will not be able to put files on the server outside this directory (tho SSH Exec command is free to do anything that the configured user is free to do) Advanced optionsĬlicking the "Advanced" button will reveal the following options. If the directory is not supplied, then the effective root directory will be the directory which the user is in when they login using the credentials supplied. If not absolute, then the directory will be relative to the directory which the user is in when they login using the credentials supplied. If specified, the remote directory must exist, it will not be created. Make sure that you backup $JENKINS_HOME/secret.key Remote directoryĪ directory on the remote server that will serve as the effective root directory for this configuration. The Publish Over SSH Plugin can use Username/Password, or SSH keys to authenticate when loging in as Username.įrom version 0.4 (Publish Over FTP Plugin 0.4, Publish Over SSH Plugin 0.5) the password and passphrase value is encrypted in the configuration files and also in the Jenkins UI. The Publish Over FTP Plugin uses Username/Password. Not a field in itself, but the connection will need to know how to authenticate to the remote server. The hostname must be resolvable by any of the machines that may initiate a connection to the remote server. The hostname or IP address of the server. ![]() Having a name for the configuration allows multiple configurations to the same host (to login with different users, or set different remote directories). Give the configuration a name, this is the name that appears in the drop down box on the job configuration page. If all is well, then you should see "SUCCESS", otherwise you will see a message in red which should hopefully give some information to help fixing the configuration. When first configuring or changing a configuration, always click the "Test Configuration" to ensure that the configuration will work when it is used from a Job. SSH keys, passive mode FTP, etc), but somme common options are listed below. As the host configuration specifies how to connect to the remote server, the configurations can be quite specific to the plugin (ie. To change the order that the configurations appear in the drop down on the job configuration page, drag the square icon (next to FTP/SSH server) to reorder the list. Publish to other servers if an error occursĬreate one or more configurations that can be selected from the job configuration page. ![]()
0 Comments
Leave a Reply. |