Remove the ability to run Exec commands from this plugin.
26 |The Disable exec in the advanced settings for individual configurations will be ignored.
The private key.
27 |Paste the private key here, or provide the path to the file containing the key in Path to key.
28 |
The path to the private key.
27 |Either supply the path to the file containing the key, or paste the key into the Key box.
28 | The Path to key can be absolute, or relative to $JENKINS_HOME
29 |
Key or Path to key is
26 | configured.The private key.
27 |Paste the private key here, or provide the path to the file containing the key in Path to key.
28 |
The path to the private key.
27 |Either supply the path to the file containing the key, or paste the key into the Key box.
28 | The Path to key can be absolute, or relative to $JENKINS_HOME
29 |
Avoids to send files to remote target if they are still the same.
4 |Based on checking last modification time and MD5 hash of the resource to be uploaded
5 |The private key.
27 |Paste the private key here, or provide the path to the file containing the key in Path to key.
28 |
The path to the private key.
27 |Either supply the path to the file containing the key, or paste the key into the Key box.
28 | The Path to key can be absolute, or relative to $JENKINS_HOME
29 |
Override the default authentication key.
27 |The key is specified by pasting into the Key section, or by providing the file path to the key
28 | in the Path to key. If both are provided, then the pasted Key will take precedence.
If no key is set then the Passphrase / Password will be used for password authentication, else it is
30 | used for decrypting the key.
31 |
The base directory for this configuration.
27 |This directory must exist, it will not be created.
28 | The publisher will only be able to place files below this directory.
Note that nothing prevents an exec from creating, deleting or moving files anywhere that the user has permission 30 | to.
31 |Timeout in milliseconds for the SSH connections.
27 |Set to zero to disable.
28 |Send files or execute commands over SSH after the build runs.
26 |This will run the SSH publishers after the build has finished and will run no matter what the status of the build was.
27 | Note that if the build fails before the builders are executed (ie in a pre build step) then the post build steps will not run.
28 |
Send files or execute commands over SSH before the build runs.
27 |This will run the SSH publishers after the workspace has been checked out, but before the build starts.
28 | If the publish fails, then the build will be marked as unstable, but still continue. To fail the build set the
29 | Advanced option "Fail the build if an error occurs". This will also prevent post build steps from being run.
30 |
Select an SSH configuration from the list configured in the global configuration of this Jenkins.
27 |The configuration defines the connection properties and base directory of the SSH server.
28 |If you want to use different credentials from those configured for this server, or if the credentials have not been specified 28 | for this server, then enable this option and set them here.
29 |Set the label for this Server instance - for use with Parameterized publishing.
27 |Expand the help for Parameterized publishing for more details.
28 |If publishing to this server or command execution fails, try again.
27 |Files that were successfully transferred will not be re-sent.
28 | If Exec command is configured, but fails in any way (including a non zero exit code), then it will be retried.
29 |
Use the build time of the promotion when the remote directory is a date format.
27 |By default this plugin uses the time of the original build (the one that is being promoted) when formatting the 28 | remote directory. Setting this option will mean that if you use the remote directory is a date format option, 29 | it will use the time that the promotion process runs, instead of the original build.
30 |Set the root directory for the Source files to the workspace.
27 |By default this plugin uses the artifacts directory (where archived artifacts are stored). This allows the artifacts 28 | from the build number that you are promoting to be sent somewhere else.
29 |If you run tasks that produce files in the workspace during the promotion and you want to publish them, then set this 30 | option.
31 |If you need to send files from both the workspace and the archive directory, then you need to add a second server, 32 | even if you want to send the files to the same place. This is due to the fact that the workspace is not necessarily 33 | on the same host as the archive directory.
34 |Matrix jobs will always use the workspace as the base directory for Source files - even in promotions.
27 |The promotion process will only run once and the build artifacts are stored beneath each configuration.
28 |Set the label for this Server instance - for use with Parameterized publishing.
27 |Expand the help for Parameterized publishing for more details.
28 |Select to publish from the Jenkins master.
27 |The default is to publish from the server that holds the files to transfer (workspace on the agent, or artifacts directory on the master).
28 | Enabling this option could help dealing with strict network configurations and firewall rules.
29 | This option will cause the files to be transferred through the master before being sent to the remote server, this may
30 | increase network traffic, and could increase the build time.
Configure the private key for connecting to SSH servers.
27 |The key configured here is a default key which can be overridden for an individual host.
28 |The key is specified by pasting into the Key section, or by providing the file path to the key
29 | in the Path to key. If both are provided, then the pasted Key will take precedence.
If Passphrase is provided then it will be used to decrypt the private key.
Set the NODE_NAME for the master Jenkins.
27 |Set this option to give a value to the NODE_NAME environment variable when the value is missing (the Jenkins
28 | master).
29 | This is useful if you use the NODE_NAME variable in the remote directory
30 | option and the build may occur on the master.
Exclude files from the Transfer set.
27 |The string is a comma separated list of excludes for an Ant fileset eg. '**/*.log,**/*.tmp,.git/' 28 | (see Patterns in the Ant manual) 29 |
30 |A command to execute on the remote server.
27 |This command will be executed on the remote server after any files are transferred.
28 | The SSH Transfer Set must include either a Source Files pattern, an Exec command, or both. If both are present, the files are
29 | transferred before the command is executed. If you want to Exec before the files are transferred, use 2 Transfer Sets and move the
30 | Exec command before the Transfer set that includes a Source files pattern.
31 |
Timeout in milliseconds for the Exec command.
27 |Set to zero to disable.
28 |Only create files on the server, don't create directories (except for the remote directory, if present).
27 |All files that have been selected to transfer must have unique filenames. The publisher will stop and fail as 28 | soon as a duplicate filename is found when using the flatten option.
29 |Keep local file permissions of transferred files.
4 |Changes file permissions of the file after transferring to the local one.
5 |NB: only POSIX file permissions support is implemented.
6 |The default behaviour of this plugin is to match files, and then create any directories required to preserve the paths to the files.
27 | Selecting this option will create any directories that match the Source files pattern, even if empty.
The default exclude patterns are:
31 |