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 Qlik based on experience 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 Qlik but with certain conditions explained in notes.
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.
| GitHub version | Support type |
|---|---|
| SaaS | Recommended |
| Enterprise 3.x | Recommended |
| Enterprise 2.x | Supported |
To learn how to connect to GitHub using a personal access token, see Authorizing a personal access token for use with SAML single sign-on.
| Bitbucket version | Support type |
|---|---|
| SaaS | Supported |
| 9.x | Supported with limitations:
|
| 8.x | Supported |
| 7.x | Supported |
| Server 6.1 to 6.10 | Supported |
| Azure DevOps version | Support type |
|---|---|
| SaaS | Supported |
| TFS 2018 to latest | Supported |
| AWS CodeCommit version | Support type |
|---|---|
| SaaS | Supported |
When using AWS CodeCommit SaaS, Qlik only supports authentication with Git credentials and Personal Access Tokens.
| GitLab version | Support type |
|---|---|
| SaaS | Supported |
| 12 to latest version | Supported |
| Gitblit version | Support type |
|---|---|
| 1.8 | Deprecated |