Init local repository: Select this option to initialize a local Git repository and connect a Matillion ETL project to Git for the first time.When performing this action for the first time, you will have two options: In the top-left of the Matillion ETL user interface, click Project, then navigate down and click Git. master, Alice_Branch and Bob's_Branch also have their own Matillion ETL versions, with Alice and Bob's version serving as independent working areas for their developer work, which, when tested and approved, is merged. The rest of this article documents what actions a user can take when using Git in Matillion ETL.įor many of the sections below, a fictitious development team's example workflow is referenced in the screenshots, focusing on a master branch and a branch each for a pair of developers, Alice and Bob. Matillion ETL's Git integration feature does not support multi-factor authentication (MFA) at this time. This simply means that the local repository's changes require a push to the remote repository, at which point Commit 3 of Branch Feature_1, which is being developed in Version ver_z, will be backed up in the cloud-hosted remote repository. However, note that the remote repository is missing Commit 3 from Branch Feature_1. Shown to the right of the local repository is the remote repository, which contains a backup copy of local repository. Within each of these branches are three commits, and the diagram shows via the shorter white arrows which version is pointing at which commit. There is the master branch ( Branch Master), and an additional branch ( Branch Feature_1). Shown to the right of the project is the local repository, which contains two branches. Each of these versions might, for example, belong to an individual developer in a development team. Within this project are three separate versions. The above diagram includes an example project, project_Dev. Once the code has undergone testing, it can be merged safely into the master branch. A branch model typically allows users to develop new code without adding questionable code to the master branch. Typically, a Git project will have a master branch, from which other branches will be created to develop and test code. A branch is a collection of one or more commits in Git. A commit is a point-in-time copy of a Matillion ETL version, typically with collateral stored in the version, such as orchestration and transformation jobs. Users can also fetch newer commits from the remote repository into the local repository. Users can push local repository commits to their remote repository. A self-hosted or cloud-hosted Git repository that is external to Matillion ETL, and which you must set up prior to Git-enablement in Matillion ETL. The local repository stores files on the Matillion ETL instance's filesystem, which is created automatically when a project is Git-enabled. Each version points to a single Git commit in the local Git repository. When used with Git, think of a version as an independent working area. A project can contain more than one version. Each project is isolated, and user access can be granted or denied on a per-project basis. The project is the top-level structure containing jobs and other collateral within Matillion ETL. When using the Git version control feature in Matillion ETL, it'll help to understand the underlying architecture and concomitant technical terms. Git is an Enterprise Mode feature within Matillion ETL. Git Integration: Frequently Asked Questions.MergeManager for resolving merge conflicts.This article is part of a series of technical documentation covering the Git integration feature within Matillion ETL. This article explores the architecture of Matillion ETL's Git integration feature and documents actions including commit, create branch, merge, push, fetch, and more.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |