SSH Upload
The SSH Upload build runner allows uploading files/directories via SSH (using SCP or SFTP protocols).
The settings common for all runners are described in Configuring Build Steps; this page details the SSH Deployer settings.
The fields below support parameter references: any text between percentage signs (%
) is considered a reference to a property by TeamCity. To prevent TeamCity from treating the text in the percentage signs as reference to a property, use two percentage signs to escape them: for example, if you want to pass %Y%m%d%H%M%S
into the build, change it to %%Y%%m%%d%%H%%M%%S
.
warning
When strong cryptography is required by the server that receives the deployment, build agents need to have Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy installed on the JRE.
Option | Description |
---|---|
Deployment Target | |
Target | Target should point to an SSH server location. The syntax is similar to the one used by the *nix
where |
Transport protocol | Select a protocol to transfer data over SSH. The available options are: SCP and SFTP |
Port | Optional. By default, port 22 is used. |
Deployment Credentials | The settings in this section will vary depending on the selected authentication method. |
Authentication method | Select an authentication method.
|
Deployment Source | |
Paths to sources | Specify the deployment sources as a newline- or comma-separated list of paths to files/directories. The field supports Ant-style wildcard patterns (for example, |
Thanks for your feedback!