# How to Connect Teamscale to an Unsupported Version-Control System
Teamscale supports various version control systems. If your system is not (yet) supported, there are two ways to let Teamscale analyze your code anyway:
# 1. Connecting via Git Bridge (Recommended)
The preferred way of integration is by using the version control system Git (opens new window). Git is deeply integrated into Teamscale and there are many so-called Git bridges to other version control systems. Such a git bridge connects a version control system to git and allows bidirectional synchronization.
The following are examples for git bridges.
- Perforce: here (opens new window) and here (opens new window)
- CVS: here (opens new window)
- Mercurial: here (opens new window)
- Rational Team Concert: here (opens new window)
If your version-control system is not listed, try a web search to see if a git bridge for your system is available.
To setup Teamscale with such a version control system, configure the git bridge and ensure that a local clone of this repository is kept up to date (e.g., by calling
git pull from a cron job).
Then connect Teamscale to this local clone using the regular Git repository connector.
Support for Git Bridges
Please note that we cannot provide support for these Git bridges, as they are developed by third parties.
# Connecting via File System Connector
The second solution uses a simple check out as a fallback that can be used if no git bridges are available. This solution, however, cannot store a permanent history of the code base as it will be lost upon restarting Teamscale.
To configure this, create a local check out of your code base and ensure that the check out is kept up to date (e.g., by running a cron job with the corresponding update command). Then configure Teamscale with the file system connector for the check out directory. As the file system connector is polling continuously for changes, any detected file changes will lead to virtual commits and automatically processed by Teamscale.