Server
The URI of the Team Foundation Server. The URI pattern is [protocol]://[domain]:[port]/tfs/[collectionname]/
...
If you are using the hosted version of TFS and you are having difficulty connecting, try specifying the [collection name] at the end of the server path.
Note: If your TFS or VSTS repository is a Git repository, use the Git repository type.
TFS Version
TFS 2010, 2012, 2013, 2015 and 2015 2017 have been tested and work correctly with Continua CI. Older versions may also work with Continua CI.
Team Project Path
The team project you want to link to Continua CI. The path must start with $.
The path is usually in the format of $/myproject.
Relative Folder
The path to a relative folder under the Team Project. Use this to restrict checking and exporting of the repository source to a specific folder.
Credentials
...
- Single branch
This option tells Continua CI to monitor only the single branch you specify.
When you select this option you need to provide a Branch Path which is the path of the branch you want ContinuaCI to monitor. The Branch Path should start with / and is usually in the format of /mybranch. If you want to monitor from the root of the repository and exclude any branches, then you can leave the Branch Path blank or enter /.
You can also specify a Relative Folder Under Branch. This allows you to restrict checking and exporting of the repository source to a specific folder under the branch. All branches
This option tells Continua CI to monitor all branches in the repository.
When you select this option you need to provide a Default Branch path so Continua CI knows what to use for a build when no branch is selected. The Default Branch should start with / and is usually in the format of /mybranch. If you want Continua to get code from root of the repository by default, excluding any branches, then you can leave the Default Branch blank or enter /.
By default any changes in folders which are not part of a TFS branch will be associated with a root branch path "/" displayed as "no branch". Tick the Exclude changesets not in a branch checkbox to exclude these changesets.
You can also specify a Relative Folder Under Branch. This allows you to restrict checking and exporting of the repository source to a specific folder under each branch. Note that no changesets will be picked up from any branches which do not include this relative folder.
If you enter a non-zero Maximum Branch Age, then branches with commits or builds older than the specified number of days will be hidden from Start Build and Trigger dialogs.
- By pattern
This option tells Continua to monitor any branch that matches a pattern you provide in the Branch Pattern field. The Branch Pattern field accepts a regular expression which is matched against all the branches in your TFS repository.
Since the pattern can potentially match more than one branch, you also need to provide a Default Branch value so Continua knows what to use for a build when no branch is selected. The Default Branch should start with / and is usually in the format of /mybranch. If you want Continua to get code from root of the repository by default, excluding any branches, then you can leave the Default Branch blank or enter /.By default any changes in folders which are not part of a TFS branch will be associated with a root branch path "/" displayed as "no branch". Tick the Exclude changesets not in a branch checkbox to exclude these changesets.
You can also specify a Relative Folder Under Branch. This allows you to restrict checking and exporting of the repository source to a specific folder under each branch. Note that no changesets will be picked up from any branches which do not include this relative folder.
If you enter a non-zero Maximum Branch Age, then branches with commits or builds older than the specified number of days will be hidden from Start Build and Trigger dialogs.
- Ignore branches
...
The Paths tab allows you to specify the path that the source code is exported to. By default the source is exported relative to the folder under the branch path. You can choose to Include the relative folder under the branch when exporting. You can additionally Include the branch path and Include the relative folder. Note if you choose to include the branch path than you must also include the relative folder under the branch if one is specified. Likewise, if you include the relative folder, the branch path and relative folder under the branch must also be included if these are specified.
You also have the option to include the branch path when exporting the source code from the repository. By default the source is exported with the branch path as the root.