Management → Managing Components → Creating Components → Source Configuration Type Fields → TFS vNext
Microsoft Visual Studio Team Foundation Server (TFS) is the collaboration platform at the core of Microsoft's application lifecycle management (ALM) solution. For more information on using TFS, see the Microsoft documentation.
The TFS vNext source configuration type is implemented as an external type and is to be used with TFS 2015 and 2017. If you are using earlier versions of TFS, see TFS.
Select TFS vNext from the Source Config Type drop-down list box and then configure the type-specific fields described here. For information about creating components, see Creating Components.
When you import a version for a component that uses this source configuration type, you are prompted for build number. There you should enter the build that has the artifacts you want to import. If you leave it blank, the latest build's artifacts are imported.
|TFS URL||Specify the TFS
server URL. For example:
|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||
If this is selected, the current component properties are used to download this component's version artifacts in Versions > Artifacts. You should deselect this if the component's storage location or connection details have changed since the version artifacts you want to download were imported, so that the component properties that were set when the version was created are used instead. See Maintaining Versions Externally.
|Copy to CodeStation||
This option, selected by default, creates a tamper-proof copy of the artifacts and stores them in the embedded artifact management system, CodeStation. For optimal use of Deployment Automation, the check box should be selected.
If you deselect Copy to Codestation for this source configuration type, pointers to versions are saved in Deployment Automation rather than the versions themselves. This enables you to track the versions, but limits some functionality in Deployment Automation. See Maintaining Versions Externally.
Copyright © 2011–2018 Serena Software, Inc., a Micro Focus company. All rights reserved.