Share this page
TFS vNext SCT
You can use Microsoft Visual Studio Team Foundation Server (TFS) as an artifact source for a component.
Guidelines
The TFS vNext source configuration type (SCT) is implemented as an external type and can be used with TFS 2015 and 2017. For earlier versions of TFS, see TFS SCT.
To use TFS vNext as an artifact source, select TFS vNext from the Source Config Type list and specify its properties. For details about creating components, see Create components.
Tip: When you import a version for a component that uses this source configuration type, you are prompted for build number. Enter the build that has the artifacts you want to import. If you leave it empty, the latest build's artifacts are imported.
Note: TFS vNext brings built artifacts from TFS into Deployment Automation. To bring TFS source-controlled artifacts into Deployment Automation, see TFS_SCM SCT.
If TFS build artifacts are published to a network share, ensure that the Deployment Automation application server, Common Tomcat, is running under a user account that has access to that network share. For details, see Install server.
TFS vNext SCT settings
To use the TFS vNext source configuration type (SCT), you need to specify the following settings:
| Field | Description |
|---|---|
| TFS URL |
Specify the TFS server URL, for example: http://tfs2017:8080/tfs/DefaultCollection |
| TFS Username | A username that can access the TFS API. |
| TFS Access Token |
If using access tokens, specify a valid TFS access token for a TFS user with build (read) permissions. If using basic authentication, specify the user password. Note: The TFS vNext source configuration type is implemented using the REST API. Access tokens can be created to access the REST API in TFS 2017. This access token must have build (read) permission. |
| TFS Team Project | The name of the TFS team project where the build definition resides. |
| Build Definition | Specify the name of the build definition to monitor for new builds. |
| Build Result | Select one or more results to limit the builds that are eligible for version import. |
| Use Latest Component Properties for Version Download |
(Optional) Select this option if you want Deployment Automation to use the current component properties instead of the properties that are set when the version is created. Note: Component version properties are always preserved when a version is created. |
| Copy to CodeStation |
(Optional) Use this option to create a tamper-proof copy of the artifacts and store them in the DA's embedded repository, CodeStation. For optimal use of Deployment Automation, we recommend that this option is selected. Clear the option to save pointers to versions rather than the versions themselves. This way, you can track versions and save space on your Deployment Automation server, but this limits your ability to download individual versions. For details on maintaining versions in external sources, see CodeStation: maintain versions externally. |
See also:
