Git Integration Frequently Asked Questions
This page is a compiled list of frequently asked and salient questions about the Matillion ETL Git integration feature, which lets Matillion ETL users track a project's changes—both small and large—with speed and efficiency via Git source control management.
This article is part of a series of technical documentation covering the Git integration feature within Matillion ETL. Additional documentation includes:
- Git Integration.
- Git Integration: API.
- When To Choose Git.
- Users should note that Git is an "enterprise" feature within Matillion ETL. To learn more about Matillion ETL Enterprise Mode and how to upgrade your licence, please click here.
Frequently Asked Questions
Can I connect Matillion ETL to an existing Git repository that contains non-Matillion ETL items?
No, we do not advise this. Matillion ETL should have sole use of a Git repository.
Can I use Matillion ETL's built-in versioning system in combination with Git?
Matillion ETL's built-in version system will continue to operate as normal once you have converted your Matillion ETL project into a Git project. Users have the ability to switch version between Git commits. Rather than running two version control strategies in parallel, we recommend that you use Matillion ETL versions as independent "working areas" to isolate your developers, or to separate one feature development effort from another. Read Manage Versions to learn more.
When creating a new version, Matillion ETL makes a clone of the project and the jobs. This means that new job IDs are created for each job. If you are using Git integration with Matillion ETL, checkout the branch you are using to avoid merge conflicts for each job.
Can I use the Git command line tools?
Matillion ETL uses a library to communicate with Git directly, so the command line tools are not supplied by default when connecting via SSH to the Matillion ETL instance. While the command line tools can be installed, we do not recommend manually using Git tools to amend your repository from outside Matillion ETL.
Do you recommend using Git for my Matillion ETL version control?
Git is a complex tool, enabling users to devise intricate development workflows. Unless your company mandates Git usage, or unless you are familiar with Git working patterns, you might find that Matillion ETL's built-in versioning, or other methods for migrating jobs between Matillion ETL projects, better suits your work requirements.
How does authentication work between my local repository and my remote repository?
Authentication type depends on your chosen security protocol. For
HTTPS, users will need to provide their remote repository account's username and password. Users must then additionally select the encryption type.
Alternatively, if users authenticate with the
SSH security protocol, users must provide a valid private key and passphrase. We recommend users read this GitHub article on choosing which remote URL to use.
Can I use multi-factor authentication (MFA) with Git integration in Matillion ETL?
Matillion ETL does not support multi-factor authentication for its Git integration feature at this time.
How do I push a single branch?
When performing a push command, Matillion ETL will push all branches by default. Currently, users do not have the option to change this setting.
Working with GitLab leads to a "Loading. Please wait..." when I try to push to my Git repo. Why is this?
If your remote repo is hosted at GitLab and you are having issues performing a push command from Matillion ETL to GitLab, please read this GitLab blog post and follow the instructions.
If you have a question this page has not yet answered, please contact support.