The Git repository created and automatically maintained by MettleCI is…
/
├── datastage/ # This structure is automatically managed by MettleCI
│ ├── default.apt # The apt config file for your project
│ ├── DSParams # The DSParams for your project
│ ├── Jobs/ # The structure under the root 'datastage' folder directly reflects
│ │ ├── Extract/ # the structure in root of your DataStage repository. Every time
│ │ │ ├── ExtractJob_One # you check in datastage assets the required folders are created for
│ │ │ ├── ExtractJob_Two # you in your git repository.
│ │ │ └── ...
│ │ ├── Load/ #
│ │ │ ├── LoadJob_One #
│ │ │ ├── LoadJob_Two #
│ │ │ └── ...
│ │ ├── Transform/ #
│ │ │ ├── TransformJob_One #
│ │ │ ├── TransformJob_Two #
│ │ │ └── ...
│ │ └── ...
│ └── Parameter Sets/ # Directly reflecting the folder in root of your DataStage repository
│ ├── SourceDB1/ #
│ │ └── source1 #
│ ├── SourceDB2/ #
│ │ └── source2 #
│ ├── TargetDB/ #
│ │ └── target #
│ └── pGlobal/ #
│ └── global #
├── filesystem/ #
│ ├── datasets/ #
│ ├── deploy.sh # The operating system script invoked by MettleCI during deployment
│ └── scripts/ # The scripts invoked by your deploy.sh during deployment
│ ├── 10-restore-backups.sql # Use any names/folders. This example uses numbers to imply structure
│ ├── 20-create-test-data.sql #
│ └── ...
├── unittest/ # This flat structure is automatically managed by MettleCI
│ ├── ExtractJob_One/ # Each job gets its own folder in the unittest folder
│ │ ├── dsDataSource1.csv # A test data input file
│ │ ├── dsDataSource2.csv # A test data input file
│ │ ├── dsDataSource3.csv # A test data input file
│ │ ├── dsDataTarget1.csv # A test data output file
│ │ ├── ExtractJob_One.yaml # The test specification, associating files to your job's links
│ ├── ExtractJob_Two/ #
│ │ ├── {similar to above}
│ ├── LoadJob_One/ #
│ │ ├── {similar to above}
│ ├── LoadJob_Two/ #
│ │ ├── {similar to above}
│ ├── TransformJob_One/ #
│ │ ├── {similar to above}
│ ├── TransformJob_Two/ #
│ │ ├── {similar to above}
│ └── ...
├── var.ci # Variable override files provide environment-specific values for
├── var.dev # each target deployment environment.
├── var.prod # Search the MettleCI documentation for 'variable override files'
├── var.qa # These files cov er the CI, DEV, PRO, QA, and UAT environments
└── var.uat #