This approach will be quicker.  You will need to ensure you follow this procedure on a machine with When you have a large DataStage project which you wish to get under Git version control it would be onerous to have to commit each individual artefact using the MettleCI Workbench individually. A much more efficient approach to use the MettleCI Command Line Interface. This procedure requires your computer to have both a Git client and the MettleCI Command Shell, as well as the Line Interface installed. The primary input to the process is a whole-of-Project 'archive' ISX files for each Project you wish to be brought import into Git.

...

Initial commit procedure

1. Ensure you have already installed the MettleCI Command

...

1. Extract command-shell-0.0.1-SNAPSHOT.zip from the MettleCI Installation Media
2. Copy the dm-isexport-plugin-1.0-335.jar file from the MettleCI Installation Media to the plugins directory of the extracted command-shell

Initial commit procedure

...

1. Line. 

2. Ensure that the DataStage project ISX file(s) you wish to commit are available on your machine.

3. Use your

...

1. Git client to clone the

...

1. remote Git repository you will be checking into.  Ensure the current branch is

...

1. master.

2. Check whether the cloned Git repository has a datastage directory at the root.

...

1. If this doesn't exist create it now. This folder is mandatory in order for MettleCI's automated deployment function to operate correctly.

2. Check whether the cloned Git repository has a filesystem directory at the root.

...

1. If this doesn't exist create it now. This folder is mandatory in order for MettleCI's automated deployment function to operate correctly.

2. Navigate to the command shell folder and locate the mettleci.cmd file.

3. Run the command shell by executing either the

...

1. mettleci or

...

1. mettleci.cmd from the command line. This will start an interactive session, the current working directory does not matter.

2. Run the isx cut command to split the project ISX file(s) into a temporary directory, this step can be repeated multiple times if there is more than one ISX for a given project.

...

1. Documentation of this command can be found here.

2. The cut ISX files will be dumped into your temporary directory in the following directory structure <ISX source engine name>/<ISX source project name>/<category name - recursive>/<Job Name>.isx

3. Copy all ISX files and directories from within the <source ISX project name> directory to the datastage directory of  your cloned Git repository.  The final Git repository directory structure should match datastage/<category name - recursive>/<job name>.isx

4. Use Git to add, commit and push all changes. 

...

1. Atlassian's Git tutorial

...

1. provides a good summary of how to do this.

2. Verify the commit is visible in

...

1. your Git repository against the

...

1. Master branch.

...

...

Once all production assets have been checked in, we recommend that you Tag this particular revision in case you need to quickly refer to it later in your DevOps-for-DataStage or DataStage Upgrade initiative

Tagging with Bitbucket

...

. You can tag your Git repository revision using the Git command line or, in most cases, your Git repository’s user interface.