...
| Info |
|---|
Avoiding confusion over common terms in GitHub, Bitbucket, and GitLab Despite Git being a well established standard, different vendors' Git-based version control systems can use terminology like Repository and Project differently, creating the potential for confusion. In other platforms such as GitHub and Bitbucket, “repositories” contain the Git code repository , and along with other project-related assets such as issues, contribution metrics, etc. However GitHub users often use the GitHub community often uses the terms repository and project interchangeably. In GitLabGitLab, the overarching container is called a Project. A Project includes the Git repository, issues, merge requests, milestones, and more. It's important to make this distinction because you import a Project in GitLab, regardless of whether that is called a Repository elsewhere. In GitLab, the Repository is a component part of a Project. Thus, GitLab tightly couples project and repository, and each project typically has at most may have only one Git repository. |
Note: One may keep MettleCI Compliance rules in the same repository as the DataStage assets but it’s generally recommended that a repository be dedicated to those Compliance rules intended for use by multiple pipelines (across all your DataStage-related GitLab projects). That means GitLab pipelines must be configured to explicitly clone that Compliance repository so it’s available when the pipeline reaches the Compliance execution step. The example GitLab pipeline provided with MettleCI reflects this dependency.
...