This approach is faster than on-boarding your DataStage Project via DataStage and Workbench.

This procedure requires your computer to have both the Git client and the MettleCI Command Shell installed. The primary input to the process is the whole-of-Project 'archive' ISX files for each Project to be brought into Git.

Installing the MettleCI Command Shell

See the MettleCI Command Shell installation documentation. 

Initial commit procedure

1. Ensure the DataStage project ISX file(s) you wish to commit are available on your machine.
2. Use your Git client to clone the remote Git repository you will be checking into.  Ensure the current branch is master.
3. Check whether the cloned Git repository has a datastage directory at the root. If this doesn't exist create it now. This folder is mandatory in order for MettleCI's automated deployment function to operate correctly.
4. Check whether the cloned Git repository has a filesystem directory at the root. If this doesn't exist create it now. This folder is mandatory in order for MettleCI's automated deployment function to operate correctly.
5. Navigate to the command shell folder and locate the mettleci.cmd file.
6. Run the command shell by executing either the mettleci or mettleci.cmd from the command line. This will start an interactive session, the current working directory does not matter.
7. 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. Documentation of this command can be found here.
8. 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
9. 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
10. Use Git to add, commit and push all changes.  Look at Atlassian's Git tutorial for details
11. Verify the commit is visible in Bitbucket cloud and against the master branch.

Note: This procedure will not generate preview images (of the Job on the DataStage Classic Designer client canvas) for initial commits to Bitbucket Server.  Depending on the number of projects you need to complete, this process can easily be scripted.

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

1. View your final "golden copy" commit in Bitbucket by clicking on the Commit hash link.  Ensure you are looking at the correct branch (develop).
   
   
2. Add a tag, call it PROD_BASELINE, GOLDEN_COPY or whatever you think is appropriate. 
   
   
3. You should now be able to quickly access this particular revision from within Git/Bitbucket by using the tag name. Bitbucket allows you to select this vision from within the Branch Selection drop down → Tags.