changes.
| | h2. Prerequisites |
| | QuickBuild utilizes the Team Foundation command (tf) to interact with remote Team Foundation Server repository. If this command (tf) is not in system path, you will need to specify location of the command by configuring Team Foundation Server plugin as below: |
| | !tfs-plugin.png! |
| | |
| | Further more, Team Foundation command (tf) location can be specified on a per-node basis by following below steps: |
| | # Open Team Foundation Server plugin setting page and define the Team Foundation command path property as: |
| | {code} |
| | ${node.getAttribute("tfPath")} |
| | {code} |
| | # For each node that does not have Team Foundation command on system path, define the user attribute _tfPath_ to point to the actual Team Foundation path like below: |
| | !tf-path.png! |
| | |
| | *NOTE:* example above is just for demonstration, you can use any other user attribute name instead of _tfPath_. |
| | |
| | h2. Creating a Team Foundation Server Repository |
| | You may refer to [this page|Scm Support Overview] on how to add a repository. |
| | h3. Supported URL prefixes |
| | Currently, below URL prefixes are supported: |
| | * \[http://host\[:port]/path/to/branch] |
| | * \[https://host\[:port]/path/to/branch] |
| | |
| | If *https* is used, and your credential need password, you need first add the credential manually to the nodes which you want check out code to. |
| | |
| | For Team Foundation Server 2010, the path should be a collection path, for example, http://myserver/tfs/DefaultCollection. |
| | |
| | h2. Label the source code |
| | To label the source code, you can add a label step from the configuration workflow definition page. |
| | | {note} |
| | For Team Foundation Server, you must run the label step on the same node that you run check out step. |
| | {note} |
Working with Team Foundation Server