About Version Control (VCS) for TDV
You can use TDV with popular version control systems. Version control helps track changes and gives control over changes to TDV resources. For centralized version control, check-outs and check-ins are done to a repository. For distributed version control, changes can be merged into any branch.
Each version control system interacts with TDV a little differently. We recommend setting up some test projects so that you can get familiar with how your resources will behave. For example, tasks like check in, attach, specifying connection information can vary depending on the version control tool you implement.
Supported Default Version Control Systems
By default, the supported version control systems are:
• SVN client version 1.9.5 and higher
• SVN server version 1.7 and higher
SVN, HTTP, HTTPS protocols supported. SVN+SSH not supported.
• GIT client version 2.11 and higher
• GIT server version 1.7 and higher
GIT, HTTP, HTTPS protocols supported (support one way SSL authentication with certificate). GIT+SSH not supported
• Visual Studio Team Foundation Server 2015 (TFS) with a Git Front-end is supported for HTTP protocol with NLTM authentication only.
Requirements
• Version control for TDV does not support clusters.
• The TDV VCS user must have access tools rights to access the VCS.
• Configure the GIT VCS temp directory using the Temp Directory configuration parameter (Studio - Configuration - Server - Configuration - Files - Temp Directory (On Server Restart)). For example, set it as D:/temp/vcs.
• The system PATH environment variable must include the full path to your SVN or GIT instance.
• If encrypting resources when they are checked into VCS, you must communicate and share the encryption key that you used with others that are authorized to access those resources. There is currently no automatic way to securely share encryption keys between different TDV users.
Limitations
• Renaming, moving, or reverting changes to a resource in VCS sometimes renders related resources incapable of synchronization.
• When archiving (backup or export) TDV resources if you are a non-admin user, security information is lost. When archiving (backup or export) TDV resources if you are a admin user, security information is retained.