Team Services | TFS 2017 | TFS 2015 | Previous versions (XAML builds)
Copy files to remote machines.
Use this task to copy application files and other artifacts such as PowerShell scripts and PowerShell-DSC modules that are required to install the application on Windows Machines. It uses RoboCopy, the command-line utility built for fast copying of data.
|Copy files from options|
The path to the files to copy.
A comma-separated list of machine FQDNs or IP addresses, optionally including the port number. Can be:
The username of either a domain or a local administrative account on the target host(s).
The password for the administrative account specified above.
The folder on the Windows machine(s) to which the files will be copied.
Set this option to delete all the files in the destination folder before copying the new files to it.
|Copy Files in Parallel||
Set this option to copy files to all the target machines in parallel, which can speed up the copying process.
Arguments to pass to the RoboCopy process.
|Select Machines By||
Depending on how you want to specify the machines in the group when using the Filter Criteria parameter, choose Machine Names or Tags.
Optional. A list of machine names or tag names that identifies the machines that the task will target.
The filter criteria can be:
Clear this check box if you want to disable a step. This is a handy option if a step is not working correctly or if you need to focus on other parts of the process.
Tip: You can also right-click the build step to toggle this setting.
|Continue on error||
If an error occurs in this step, and this check box is:
|Always run||Select this check box if you want the step to run even if the build is failing.|
|Timeout||The timeout for this task in minutes. The default is zero (infinite timeout).|
Do I need a build agent?
You need at least one agent to run your build. Get an agent.
I can't select a default agent queue and I can't queue my build. How do I fix this?