Compatible version control systems
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.
| GitHub version | Support type |
|---|---|
| SaaS | Recommended |
| Enterprise 3.x | Recommended |
| Enterprise 2.x | Supported |
The compatible GitHub versions support the following authentication types: HTTPS, Personal Access Tokens, SSH authorized keys.
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 |
| 8.x | Supported |
| 7.x | Supported |
| Server 6.1 to 6.10 | Supported |
The compatible Bitbucket versions support the HTTPS authentication.
| Azure DevOps version | Support type |
|---|---|
| SaaS | Supported |
| TFS 2018 to latest | Supported |
The compatible Azure DevOps versions support the HTTPS and SSH authentication types. SSH authentication requires the 8.0 R2024-07 Talend Studio monthly update or a later one.
| AWS CodeCommit version | Support type |
|---|---|
| SaaS | Supported |
The compatible AWS CodeCommit versions support the following authentication types: HTTPS and SSH authorized keys.
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 |
The compatible GitLab versions support the HTTPS authentication.
| Gitblit version | Support type |
|---|---|
| 1.8 | Deprecated |
The compatible Gitblit versions support the following authentication types: HTTPS and SSH authorized keys.