Skip to main content Skip to complementary content

Compatible version control systems

The following table provides information on the recommended and supported version control systems you can use to store your Talend projects.

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.
Availability-noteDeprecated

Apache Subversion version control servers

Version control servers Version Compatible Apache Subversion Support type
VisualSVN Server1 4.3 Apache Subversion 1.14 Supported
4.1 Apache Subversion 1.10 Supported
4.0 Apache Subversion 1.10 Supported
3.9 Apache Subversion 1.10 Supported
Bitnami Subversion Stack 1.12 - Supported
SVNEdge 5.2 Apache Subversion 1.8 Deprecated

1 VisualSVN Server does not support Integrated Windows Authentication (NTLM) method.

Git version control servers

Version control servers Version Support type Authentication type
GitHub SaaS Recommended HTTPS

Personal Access Tokens5

SSH authorized keys

Enterprise 2.X Recommended
Bitbucket1 SaaS Supported HTTPS
Server 5.10 to 7.16 Supported
Azure DevOps SaaS3 Supported HTTPS
TFS 2018 to latest 4 Supported
AWS CodeCommit SaaS Supported HTTPS

SSH authorized keys

GitLab SaaS Supported HTTPS
GitLab 2 12 to latest version Supported
Gitblit 1.8 Deprecated HTTPS

SSH authorized keys

Information noteNote: 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.

1 Compatibility checked with Bitbucket versions 5.6 and 5.10. Talend assumes that all minor versions of 5.x are backwards compatible. To see the changes between versions, see the Bitbucket upgrade matrix.

2 Latest version (with backward compatibility to GitLab 12)

3 Formerly Azure VSTS.

4 Formerly Azure TFS.

5 To learn how to connect using a personal access token, see Authorizing a personal access token for use with SAML single sign-on.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!