FTP Upload task
Azure Pipelines | Azure DevOps Server 2019 | TFS 2018 | TFS 2017
Use this task in a build or release pipeline 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, service connections are called service endpoints, stages are called environments, and jobs are called phases.
# FTP upload # Upload files using FTP - task: FtpUpload@2 inputs: #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 rootDirectory: #filePatterns: '**' #remoteDirectory: '/upload/$(Build.BuildId)/' #clean: false #cleanContents: false # Required when clean == False #preservePaths: false #trustSSL: false
|FTP service connection||
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, e.g.
Secure connections will always be made regardless of the specified protocol (
|Source folder||The source folder to upload files from. The default file path is relative from the root folder of the repo (same as if you had specified
|File patterns||File paths or patterns of the files to upload. Supports multiple lines of match patterns. To upload the entire folder content recursively, specify
|Remote directory||Upload files to this directory on the remote FTP server.|
|Clean remote directory||Recursively delete all contents of the remote directory before uploading.|
|Overwrite||Overwrite existing files in the remote directory.|
|Trust server certificate||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).|
This task is open source on GitHub. Feedback and contributions are welcome.
Q & A
Where can I learn more about file matching patterns?
Q: I'm having problems. How can I troubleshoot them?
A: Try this:
On the variables tab, add
system.debugand set it to
true. Select to allow at queue time.
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?
$(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. Get an agent for Linux, macOS, or Windows.
I'm having problems. How can I troubleshoot them?
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.