Management → Managing Components → Creating Components → Source Configuration Type Fields → TFS
Microsoft Visual Studio Team Foundation Server (TFS) is the collaboration platform at the core of Microsoft's application lifecycle management (ALM) solution.
To use TFS as an artifact source, select TFS 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.
Before you can use TFS Source Config Type, ensure the following prerequisites are met.
The Deployment Automation server installer in Deployment Automation version 5.1.5 and later automatically installs the supported tftool executables. These are placed in the Deployment Automation server tools\tfs directory in folders that match each exe name. For example, the tftool2013.exe is installed here by default:
C:\Program Files\Micro Focus\Deployment Automation Server \tools\tfs\tftool2013\tftool2013.exe
"You must provide a valid TFS tool; C:\Program Files\Micro Focus\Deployment Automation Server \tools\tfs\tftool2013\tftool2013.exe was not found."
tfsToolLocation=C:\Program Files\Micro Focus\Deployment Automation Server \tools\tfs
|TFS Server URL. Example: http://tfs2010:8080/tfs/mygroup
|The version of the TFS libraries installed on the Deployment Automation server.
|Specify a username if you need to use different credentials than the ones used for the Deployment Automation process.
|Specify a password if you specified a username.
|TFS Team Project
|The name of the TFS Team Project where the build definition resides
|The name of the build definition to monitor for new builds
|Limit builds to a given status.
|Limit builds to a given build quality.
|Directory offset within the root of the build artifacts
|Specify a new-line-separated list of files to include. Leave blank or use **/* to include all.
Specify a new-line-separated list of files to exclude.
Copyright © 2011–2017 Serena Software, Inc., a Micro Focus company. All rights reserved.