Page tree
Skip to end of metadata
Go to start of metadata


On this page:

Target audience:

CAST Administrators

Summary: Information about extracting source code from an TFS - Team Foundation Server repository using the CAST Delivery Manager Tool.
Note that the TFS - Team Foundation Server configuration in the CAST Delivery Manager Tool is not currently provided as an extension (such as for CVS and Git), instead it is provided "out-of-the-box" in CAST AIP/CAST Delivery Manager Tool.

Description

This configuration provides the means to extract source code from a Team Foundation Server (TFS) repository. In other words, file based source code that does not reside in a simple local or network folder. 

Interface

When adding a new source code package, choose the TFS - Team Foundation Server option and click Next to continue:

Click to enlarge

When selected, the above item provides the following screen with the Team Foundation Server using webservice API option already selected:

Click to enlarge

The Package Configuration tab will then be displayed, enabling you to configure access to the source code:

Click to enlarge

OptionExplanation
1Enter the URL of your Team Foundation Server repository. You can use the http:// or https:// protocols.
2Enter the repository path you are targeting - start the path with the $ sign.
3Enter the specific revision of source code that you require: T for the most recent version, or enter the specific changeset number.
4Tick the Credentials option if the TFS repository requires authenticated access. Do not enable this option if a single sign on system is in operation in your environment.
User nameUsed to configure the User name for the target Team Foundation Server 2010 repository for extraction purposes.
PasswordUsed to configure the password (in encrypted format) that corresponds to your User name configured above.
Remember password

This option enables you to force the CAST Delivery Manager Tool to save the Team Foundation Server repository access credentials you have entered above. Choosing an option or not has no impact on the analysis (i.e. the analyzer can still run an analysis). However, if you are creating subsequent Versions using the same Team Foundation Server repository, you can choose to store the password in which case you will not need to re-enter it.

There are two save options:

  • Local > The credentials are saved in the user's local workspace on the current machine. Choose this option if you do not want the password to be available to other Delivery Managers.
  • Server > The credentials are saved locally (as above) and are also synchronized back to the CAST AIC Portal (i.e. the Source Code Delivery Folder). Choose this option if you want the password to be available to other Delivery Managers.
  • No labels