FTP Upload task

Azure Pipelines | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 | TFS 2017

Use this task to upload files to a remote machine using the File Transfer Protocol (FTP), or securely with FTPS.


In Microsoft Team Foundation Server (TFS) 2018 and previous versions, build and release pipelines are called definitions, runs are called builds, service connections are called service endpoints, stages are called environments, and jobs are called phases.



YAML snippet

# FTP upload
# Upload files using FTP
- task: FtpUpload@2
    #credentialsOption: 'serviceEndpoint' # Options: serviceEndpoint, inputs
    #serverEndpoint: # Required when credentialsOption == ServiceEndpoint
    #serverUrl: # Required when credentialsOption == Inputs
    #username: # Required when credentialsOption == Inputs
    #password: # Required when credentialsOption == Inputs
    #filePatterns: '**' 
    #remoteDirectory: '/upload/$(Build.BuildId)/' 
    #clean: false 
    #cleanContents: false # Required when clean == False
    #preservePaths: false 
    #trustSSL: false 


Argument Description
Authentication Method
(Required) Use FTP service connection or enter connection credentials
Default value: serviceEndpoint
Argument aliases: credentialsOption
FTP Service Connection
(Required) Select the service connection for your FTP server. To create one, click the Manage link and create a new Generic service connection, enter the FTP server URL for the server URL, Example, ftp://server.example.com, and required credentials.
Secure connections will always be made regardless of the specified protocol (ftp:// or ftps://) if the target server supports FTPS. To allow only secure connections, use the ftps:// protocol. For example, ftps://server.example.com. Connections to servers not supporting FTPS will fail if ftps:// is specified.
Server URL
Root folder
(Required) The source folder to upload files from
Argument aliases: rootDirectory
File patterns
(Required) File paths or patterns of the files to upload. Supports multiple lines of minimatch patterns. More Information.
Default value: **
Remote directory
(Required) Upload files to this directory on the remote FTP server.
Default value: /upload/$(Build.BuildId)/
Argument aliases: remoteDirectory
Enable UTF8 support
(Optional) Enables UTF-8 support for the FTP connection ('OPTS UTF8 ON')
Default value: false
Delete remote directory
(Required) Delete the remote directory including its contents before uploading
Default value: false
Clear remote directory contents
(Required) Recursively delete all contents of the remote directory before uploading. The existing directory will not be deleted. For better performance, consider using Delete remote directory instead
Default value: false
Preserve file paths
(Required) If selected, the relative local directory structure is recreated under the remote directory where files are uploaded. Otherwise, files are uploaded directly to the remote directory without creating additional subdirectories.
For example, suppose your source folder is: /home/user/source/ and contains the file: foo/bar/foobar.txt, and your remote directory is: /uploads/.
If selected, the file is uploaded to: /uploads/foo/bar/foobar.txt. Otherwise, to: /uploads/foobar.txt
Default value: false
Trust server certificate
(Required) Selecting this option results in the FTP server's SSL certificate being trusted with ftps://, even if it is self-signed or cannot be validated by a Certificate Authority (CA).
Default value: false
FTP Commands
(Optional) Optional FTP Commands that will be sent to the remote FTP server upon connection

Open source

This task is open source on GitHub. Feedback and contributions are welcome.


Where can I learn more about file matching patterns?

File matching patterns reference

Q: I'm having problems. How can I troubleshoot them?

A: Try this:

  1. On the variables tab, add system.debug and set it to true. Select to allow at queue time.

  2. In the explorer tab, view your completed build and click the build step to view its output.

The control options arguments described above can also be useful when you're trying to isolate a problem.

Q: How do variables work? What variables are available for me to use in the arguments?

A: $(Build.SourcesDirectory) and $(Agent.BuildDirectory) are just a few of the variables you can use. Variables are available in expressions as well as scripts; see variables to learn more about how to use them. There are some predefined build and release variables you can also rely on.

Do I need an agent?

You need at least one agent to run your build or release.

I'm having problems. How can I troubleshoot them?

See Troubleshoot Build and Release.

I can't select a default agent pool and I can't queue my build or release. How do I fix this?

See Agent pools.

I use TFS on-premises and I don't see some of these features. Why not?

Some of these features are available only on Azure Pipelines and not yet available on-premises. Some features are available on-premises if you have upgraded to the latest version of TFS.