MettleCI works with assets that are kept in Git repositories, notably the repository associated with a DataStage project and the repository associated with the compliance rules. So part of the set up and integration process involves configure these within GitLab. Unfortunately GitLab uses terms in somewhat different ways than other similar tools which can lead to confusion.
| Info |
|---|
From teams to repositories to organizations, there’s potential for fresh confusion. In Comparing confusing terms in GitHub Bitbucket and GitLab Despite Git being a well established standard, different vendors' Git-based version control systems can each use terminology like Repository and Project differently, creating the potential for confusion. In other platforms such as GitHub, repositories contain the Git /SVN code repository, and the other project-related assets such as issues, contribution metrics, etc. However GitHub users often refer to repos as projects interchangeably. So in use the terms repository and project interchangeably. In GitLab, we call that container a Project. That includes the Git repository, issues, merge requests, milestones, and much more. It's important to make this distinction because you import a project in a Project in GitLab, regardless of whether that is called a repository elsewherea Repository elsewhere. In GitLab, the repository is part of a project. |
Thus GitLab tightly couples project and repository, and each project typically has at most one git repository.
...