...
The directory supplied to the -project-cache option is the location where the CLI will read/write state information (which we sometimes refer to as asset fingerprints) used for performing incremental operations. This directory should exist wherever the MettleCI CLI executes a commands command which relies on incremental behaviour, which normally occurs on the MettleCI Agent host under the instruction of your build agent.
...
In the sample pipelines shipped with MettleCI the incremental MettleCI CLI commands, assume the use of a locally-stored project cache and refer to the following project cache location:
...
| Info |
|---|
Note that the project cache will always be a Windows-style filesystem reference (using backslashes), as many of the MettleCI CLI commands required in a CI/CD pipeline must run on Windows. |
...
The directory must be unique to a DataStage project
It must be directly accessible from the CLI (iei.e.. You can't specify an engine path if the CLI is running on a Client)
If multiple instances of the CLI are to be used for incremental operations (and hence multiple independent CLI instances need to share a common view of the incremental environment’s status) then theStatus colour Red title ADVANCED -project-cacheneeds to be available and synchronised across all of those CLI instances. This is normally achieved using shared storage.
...