There are two ways to analyze code in a version control system that is not yet supported by Teamscale.
The preferred way of integration is by using the version control system git. 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, but if your version control system is not listed, try a web search to see if a git bridge for your system is available. Please note that we can not provide support for these git bridges, as they are developed by third parties.
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 git repository connector.
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, does not support analysis of the history of a code base and history 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 new commits will be detected and automatically processed by Teamscale.