Take a look at a demo of MettleCI’s Git integration here:
MettleCI’s Git integration offers a number of benefits over a Git integration you’re likely to code yourself, and over IBM's native Git integration introduced in DataStage v11.7.
In summary, MettleCI’s Git integration…
is compatible with every version of Git available, whether hosted on premises or on the cloud (unlike IBM’s)
is compatible with DataStage v8.5 onwards, easing the upgrade path for users of older versions of DataStage
is compatible with Parallel Jobs, Server Jobs, and Job Sequences, Parameter Sets, Shared Containers, QualityStage Standarization Rules, or any other DataStage artefact you want to mange in Git.
provides a live work item lookup facility enabling you to link your commit with requirements, defects, or service tickets. MettleCI does this by allowing you to dynamically query any number of work item management systems such as Atlassian Jira, ServiceNow, Azure DevOps, GitLab issues, HP ALM, etc., during check in.
provides the unique ability to visualise the checked-in artefact in your Git interface of choice (for interfaces supporting custom visualisations)
Perhaps most importantly, MettleCI’s code fingerprinting process supports the movement and renaming of artefacts in your source DataStage project without creating duplicates in your Git repository. Imagine the following scenario:
You create a Job called Cust_Extract_Job in the Jobs/ folder of your DataStage repository, and check it in to Git.
You move that job into a subfolder Jobs/Extracts/, modify it, and check it in to Git.
You rename that job to Customer_Extract_Job, modify it again, and check it in to Git.
With IBM’s native Git integration (and possibly your own) you'll end up with three distinct versions of the same job in your Git repository. With MettleCI you’ll only have one as MettleCI’s fingerprints enable it to recognise the link between artefacts in your DataStage repository and your Git repository.