...
You shouldn’t use the use the Local repository as a source of Compliance Rules outside of the MettleCI Workbench context. In particular, you shouldn’t attempt to reference a Local repository in your build (CI/CD) pipeline (it’ll work, but it’s not good practice).
The use of a Local Compliance repository does not easily support the collaborative development or maintenance of Compliance rules. For that , purpose it is recommended to use host your Compliance repository as a Remote Git repository served by a Git server. Compliance Rules are code, after all
For these reasons we recommended you always use Remote Git repositories for managing your Compliance rules.
Creating
...
your Local Repository
You can configure your local repository from your O/S command line. The example below is for
| Status | ||||
|---|---|---|---|---|
|
...
file:///opt/dm/mci/compliance/.git
| Status | ||||
|---|---|---|---|---|
|
| Note |
|---|
Note the three forward slashes after |
In all cases leave the Branch field as master blank (uses default branch, master) and the Path field empty.
...
...
See also
To When you’re ready to collaborate on Compliance Rule development, or just what to have better governance over your Compliance Rules, you may migrate your Local Git repository to a shared Remote Git repository see these instructions (page under development).