| title | description | ms.topic | ms.prod | ms.technology | ms.assetid | ms.manager | ms.author | author | ms.date | monikerRange |
|---|---|---|---|---|---|---|---|---|---|---|
Publish Build Artifacts | VSTS or Team Foundation Server |
Lear about how you can publish build artifacts to VSTS, Team Foundation Server (TFS), or to a file share when building code |
reference |
devops |
devops-cicd |
01533845-5D63-4DAC-97DF-D55F1E4DCF53 |
douge |
alewis |
andyjlewis |
10/12/2017 |
>= tfs-2015 |
VSTS | TFS 2018 | TFS 2017 | TFS 2015.3 | TFS 2015 RTM | Previous versions (XAML builds)
Publish build artifacts to Visual Studio Team Services/TFS or a file share.
Tip
Looking to get started working with build artifacts? See Artifacts in Team Build.
None
::: moniker range="vsts"
[!INCLUDE temp]
::: moniker-end
| Argument | Description |
|---|---|
| Path to publish | Path to the folder or file you want to publish. The path must be a fully-qualified path or a valid path relative to the root directory of your repository. Typically, you'll specify $(Build.ArtifactStagingDirectory). See Artifacts in Team Build. |
| Artifact name | Specify the name of the artifact that you want to create. It can be whatever you want. For example: drop |
| Artifact publish location | In most cases, VSTS/TFS (Server on TFS 2018 RTM and older) is the best and simplest option. Otherwise, choose a file share and then specify a few more arguments (see below). To learn more, see Artifacts in Team Build. |
| File share path | Specify the path to the file share where you want to copy the files. The path must be a fully-qualified path or a valid path relative to the root directory of your repository. Publishing artifacts from a Linux or macOS agent to a file share is not supported. |
| Parallel copy (VSTS, TFS 2018, or newer) | Select whether to copy files in parallel using multiple threads for greater potential throughput. If this setting is not enabled, a single thread will be used. |
| Parallel count (VSTS, TFS 2018, or newer) | Enter the degree of parallelism (the number of threads) used to perform the copy. The value must be at least 1 and not greater than 128. Choose a value based on CPU capabilities of the build agent. Typically, 8 is a good starting value. |
| [!INCLUDE control-options-arguments-md] |
[!INCLUDE temp]