MettleCI Compliance Rules are delivered as a zip file containing a ready-to-use Local Git repository. This means you can install and run Compliance Rules simply by unzipping the file to your DataStage Engine’s file system, without necessarily requiring a Git server to host a Remote repository. This is a good way to get started quickly with executing Compliance from within the MettleCI Workbench, allowing to you move towards using a Remote repository when you’re ready. In the meantime, the use of a Local repository imposes some limitations, which is why we recommended you always use Remote Git repositories for managing your Compliance rules:

• 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 host your Compliance repository as a Remote Git repository served by a Git server.

For these reasons we recommended you always use Remote Git repositories for managing your Compliance rules.

Creating your Local Repository

...

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.