Note
In the following documentation:
recommended: designates an environment recommended by Talend based on our experiences and customer usage;
supported: designates a supported environment for use with the listed component or service;
supported with limitations: designates an environment that is supported by Talend but with certain conditions explained in notes.
The following version control clients are embedded in the Talend products:
Apache Subversion (version 1.8)
Git (JGit/EGit 3.4.2)
The tables below provide a summary of the supported version control system servers that you can use to store your projects.
Table 18. Apache Subversion version control servers
|
Support type |
Version control servers |
|---|---|
|
recommended |
VisualSVN Server 3.3 (compatible with Apache Subversion 1.8) |
|
supported |
VisualSVN Server 3.5 (compatible with Apache Subversion 1.9) |
|
Bitnami Subversion Stack (compatible with Apache Subversion 1.8) | |
|
Apache svnserve/Apache httpd-2.0 with mod_dav_svn (compatible with Apache Subversion 1.8) | |
|
SVNEdge 5.1 |
The Integrated Windows Authentication (NTLM) method is not supported when using VisualSVN Server.
Table 19. Git version control servers
|
Support type |
Version control servers |
|---|---|
|
recommended |
GitHub (SaaS) |
|
GitHub Enterprise 2.12 | |
|
GitHub Enterprise 2.10 | |
|
supported |
BitBucket (SaaS) |
|
BitBucket Server 5.6 | |
|
BitBucket Server 4.8 | |
|
AWS CodeCommit (SaaS) Talend only supports authentication with Git credentials and Personal Access Tokens. | |
|
GitLab 9.1 | |
|
GitLab 8.13 | |
|
Gitblit 1.7.1 |
Note
Talend recommends that you use Talend Studio to make changes to your repository workspace, and that you use your version control system for Talend projects from Talend Studio.