The categories of data stored by MettleCI are as follows...
Registered user authentication
-
User name and company email address (recorded on first login to MettleCI Workbench).
-
Stored in a file in the MettleCI application folder on the customer’s DataStage development Engine Tier host.
-
Access (r/w) is restricted to the MettleCI Workbench service account (usually ‘mciworkb’) only and for the sole purpose of being passed to DataStage’s authentication layer whenever a user logs into MettleCI.
-
Passwords aren't stored.
Test data and Test results
-
Test data created or intercepted by users, along with sample test data records displayed in unit test reports
-
Stored in the ’specs’ and ‘reports’ folders under the MettleCI application folder on the customer’s DataStage development Engine Tier host.
-
Stored in the ‘unittests' folders in the relevant, DataStage-Project-specific repository in the customer’s Git server platform (e.g. Github Enterprise).
-
Access (r/w) is restricted to members of the the MettleCI Workbench service account’s primary group (usually ‘dstage’). This is necessary in order for Jobs to be run in a Unit Test mode by end users as well as automated CI processes.
Authentication with DataStage
-
Credentials used by MettleCI Workbench to authenticate with Information Server (either ‘dsadm’ or an account with equivalent Information Server admin privileges).
-
Encrypted using DataStage’s own encryption mechanism.
-
Stored in encrypted form in a file in the MettleCI application folder on the customer’s DataStage development Engine Tier host.
-
Access (r/w) is restricted to the MettleCI Workbench service account (usually ‘mciworkb’) only.
Authentication with supporting applications
-
Relevant applications include
-
your Git server (e.g. Github Enterprise), and
-
your work item management system (e.g. Jira)
-
-
Authentication by MettleCI Workbench is performed using SSH keys so MettleCI only records the filesystem path to the relevant private SSH key file and, optionally, a “consumer secret” value.
-
Stored in a file in the MettleCI application folder on the customer’s DataStage development Engine Tier host.
-
The SSH private keys are stored wherever the customer deems appropriate on their DataStage Engine Tier host but they must be read-able by the MettleCI Workbench service account (usually ‘mciworkb’).
-
Job metadata
-
End users can specify Job Parameters and their values in MettleCI Unit Test specifications.
-
Specification files are stored in the ’specs’ folder under the MettleCI application folder on the customer’s DataStage development Engine Tier host.
-
Access (r/w) is restricted to members of the the MettleCI Workbench service account’s primary group (usually ‘dstage’). This is necessary in order for Jobs to be run in a Unit Test mode by end users as well as automated CI processes.
-
-
DataStage assets
-
Jobs, Parameter Sets, etc…
-
During the Git commit process, these are temporarily staged (as .isx files) in the in MettleCI application folder on the customer’s DataStage development Engine Tier host.
-
Access (r/w) is restricted to the MettleCI Workbench service account (usually ‘mciworkb’) only.
-
Customers remain responsible for the safe handling of their Unit Test data in the same way as if they were testing their DataStage Jobs manually in the absence of MettleCI.