Icon

You are viewing the documentation of TeamCity 10.x and 2017.x, which is not the most recently released version of TeamCity.
View this page in TeamCity 2018.1 documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

 
Skip to end of metadata
Go to start of metadata

FTP Upload allows deploying files/directories to an FTP server.

 

The settings common for all runners are described on a separate page; this page details the FTP Upload settings. 

Icon

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 a property reference, use two percentage signs to escape them: e.g. if you want to pass "%Y%m%d%H%M%S" into the build, change it to "%%Y%%m%%d%%H%%M%%S"

OptionDescription
Deployment Target
 Target host

Specify an FTP server (usehostname or IP address) and a remote directory (relative to the FTP user's home).

To use an absolute *nix path, use %2F as the forward slash. For example:

 

hostname.com:34445/subdir
127.0.0.1/%2Fetc/
Secure connection

Choose between an insecure (FTP) and a secure connection (FTPS, FTPES).

Deployment Credentials
Authentication method Select either Anonymous (will submit username "anonymous" and a single space as the password) or username/password (for custom credentials)
FTP modes
FTP ModeSelect the passive or active mode
Transfer ModeOptional. Select an FTP transfer mode to force:  the ASCII or Binary FTP transfer modes (if the automatically detected mode leads to broken files transfer)
Deployment Source
Paths to sourcesSpecify the deployment sources as a newline- or comma-separated list of paths to files/diretories to be deployed. Ant-style wildcards like dir/**/*.zip and target directories like *.zip => winFiles,unix/distro.tgz => linuxFiles, where winFiles and linuxFiles are target directories, are supported.  

 








  • No labels