Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

MettleCI enables you to check in changed DataStage Repository-based assets (e.g. Jobs, ParameterSets...) to a Git repository. Git check-in can be performed either via a combination of the DataStage Classic Designer client and MettleCI Workbench or directly in MettleCI Workbench. The former option - while involving two pieces of software - is the quickest as it avoids manually filling out Job information (e.g. which Project it is part of) each time you commit a change.

Step-by-step guide

1.Integrate MettleCI Workbench with Datastage Client

Follow the instruction in Getting Started with MettleCI Workbench to Integrate MettleCI Workbench with DataStage Client


2. Code check in via DataStage Client

Once MettleCI Workbench and DataStage Client are integrated. You can start DataStage Client, and open a job.

When the job is opened. Start code checking from the menu 

Tools → Custom → Check-In Asset

 

From the main screen, select a project and click "Check-in a Job" button from the menu


3. Enter Commit Message

Enter the commit comments, and click "Check in" when ready

Optional

You can set the Unit Tests flag to on if you wish to check in the Unit Test assets associate with the referred DataStage Job

 


4. View Error Log 

When check-in completes, regardless of Pass or Fail, you can see the status from the VIEW LOGS at the bottom of the screen

5. Commit History

You can also review the Commit History by clicking on "Version Control" from the sidebar, you can now see the success/failure history of last code check in


6. Alternate method of Code Checkin without DataStage Client 

If you do not have a DataStage client installed on your machine. You can still perform code checkin via MettleCI Workbench frontend, by clicking on "Version Control" from the sidebar of MettleCI

Followed by click on the + button on the top right hand corner to start code check-in (then follow the steps 3 to 6 to complete the process)


















  • No labels