This feature is available to customers on specific editions. Visit Matillion pricing to learn more about each edition.
These setup steps detail what is required to connect a GitLab cloud project to . While it may be possible to connect using a GitLab self-managed instance, this is not yet officially supported.
1. Create a new GitLab repository (optional)
Once signed in to your GitLab account, create a new project in your preferred group/sub-group. We strongly recommend also initializing the repository with a README file. The repository for the project will be created withmain as the default branch.
A branch called
main is required, but it does not have to be the default branch.Want to use an existing repository?
If you already have an existing GitLab repository, you can connect it to your project, too. Once you complete the authorization process between GitLab and Matillion, you will see any existing repositories in the groups and sub-groups that you have the permission to view the source code of. If you choose an existing repository to connect to , then all existing branches will be visible in your branch list in the Branches tab.2. Set up GitLab project roles and permissions
There are numerous ways to control access of users to your GitLab projects, whether that is through the readily available roles offered by GitLab that provide collections of permissions to a user, or by defining custom roles if you need more fine-grained control. This is not intended to be a primer on GitLab access control; however, you can read more about GitLab Roles and Permissions in the GitLab documentation. If your organization is using the roles provided by GitLab, then for a user to be able to select a GitLab repository as a destination in , they will need to be assigned at least theDeveloper GitLab role or above. The only repositories exposed for selection are those that a user has write access to, meaning any custom roles will need to grant write permissions to the user.

