Creating components from Microsoft Team Foundation Server SCM
Microsoft™ Team Foundation Server SCM is a source code management tool.
Note: For IBM® UrbanCode® Deploy 6.0.0, both the agent and server must be installed on a computer that is running Windows. For versions 6.0.1 and later, only the agent must be installed on a computer that running is Windows.
- In IBM UrbanCode Deploy, click Components, and then click Create Component.
- In the Create Component window, specify a name and description for the component.
- In the Teams fields, specify the access information for the new component.
- To use a template for the new component,
select a template from the Template list.
In this case, the component inherits source configuration, properties, and processes from the template. For information about templates, see Component templates.
- In the Source Configuration Type list, select TFS_SCM.
- Specify the following parameters for the component:
- Repository URL
- The URL of the TFS repository, such as
- The user name of the TFS-credentialed user.
- The password of the TFS-credentialed user.
- tf.exe Path
- The location of the tf.exe file, for example,
C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE.
- The name of the TFS workspace. A workspace maps local and version-controlled folders on the TFS server.
- Server Folder
- The location of the TFS server folder.
- Local Folder
- The location of the workspace local folder.
- Preserve Execute Permissions
- For Linux™ and UNIX™ operating systems, select this check box to retain the execute permissions for each file.
- Extensions of files to Convert
- If text-type files must be converted into another character set, type the list of file
extensions to be converted. Matching file types are converted into the default or system character
set of the system where the agent is located. Separate list items with commas, for
- Import Versions Automatically
- Select this check box to check for new versions periodically and to import new versions automatically. If you do not import versions automatically, you can import versions manually by clicking Import New Versions. and then clicking
- Copy to CodeStation
- This option, which is selected by default, creates tamper-protected copies of the artifacts and stores them in the embedded artifact management system, CodeStation. If the check box is cleared, only metadata about the artifacts is imported. In most cases, keep this check box selected. The default for this setting is in the system setting Components copy to CodeStation by default. For more information, see Server settings.
- Default Version Type
- Specify how to import versions into CodeStation:
- Each version is comprehensive and contains all artifacts.
- Each version contains a subset of artifacts.
- Use the system's default version import agent/tag
- If this parameter is selected, the agent or tag that you specified on the System Settings page is used to import component artifacts. Agents must have access to the system where the artifacts are located. For more information, see Server settings.
- Import new component versions using a single agent
- If this parameter is selected, use the Agent for Version Imports field to identify the agent that is used to import artifacts into the component. The agent must have access to the system where the artifacts are located. To import artifacts from where the server is located, install an agent in the same location and specify that agent.
- Import new component versions using any agent with the specified tag
- If this parameter is selected, use the Agent Tag for Version Imports field to identify the tag that is used to select agents to import artifacts into the component. All tagged agents must have access to the system where the artifacts are located.
- Use Default Artifact Cleanup Settings
- To apply the component version cleanup settings that are specified on the System Settings page, select the Use Default Artifact Cleanup Settings check box. If this check box is cleared, you must specify how long to keep component versions. For more information about cleaning up component versions, see Cleaning up component versions.
- Run Process after a Version is Created
- To automatically run a process after versions are
imported, select this check box, and then specify an application process and an environment for the
process. The process runs only when the version is imported automatically, not when you import
versions manually. Similarly, the process does not run when you create versions with the REST API or
udclientcommand. If the automatic version import finds multiple versions, the process runs only once.
- Click Save.