Registering a DataStage Project with MettleCI

To enable the MettleCI Workbench to perform Compliance testing or Git Commit of DataStage Project assets a DataStage Project must first be registered with the MettleCI Workbench.

To register a DataStage Project with MettleCI log into the MettleCI Workbench and click your user avatar or user name in the top right-hand corner of the Workbench interface. From the menu which appears select Manage Projects.

Open

This will present the Registered Projects page which displays the list of DataStage projects currently registered with MettleCI.

Open

For each project listed, the page describes…

• The project name

• A check mark indicating that a Git repository for your DataStage solution has been registered for this project. Move your mouse over the check mark to see the solution repository’s Git URL.

• A check mark indicating that a Git repository containing your Compliance rules has been registered for this project. Move your mouse over the check mark to see the Compliance repository’s Git URL.

• The name of the Issue Management System associated with this project

• A set of actions buttons which, for the relevant project, permit you to (1) Edit the current project settings, or (2) De-register the project from MettleCI. Note that this second option does not delete (or in any way affect) your DataStage project.

To register a new project click the [+] icon in the top right. You’ll then be presented with the project registration wizard which will take you through a 4-step registration process:

1. Select the DataStage project you wish to register from the drop-down list.

    

    

2. You will then be prompted to provide details for your DataStage asset Git Repository.

   • In the URL field, enter either the SSH or HTTP clone string for the project. Its exact format (including whether or not you prefix it with a protocol specifier - HTTP:// or SSH://) is dependant upon the features of your selected Git system, but will generally look very much like one of the following:

     1. https://<git.domain>/<repository-name>.git for HTTP/HTTPS-based URLs, or

     2. ssh://<user>@<git.domain>:<repository-path><repository-name>.git (or something similar) for SSH-based URLs

   • For example, the SSH clone string of a remote Git repository for a DataStage Project called ‘MYDATASTAGEPROJECT’ set up in Data Migrators' Atlassian’s Bitbucket Cloud instance would be ssh://git@bitbucket.org:datamigrators/mydatastageproject.git.

   • In the Branch field enter the branch you want MettleCI to commit to. Unless you have a good reason to specify otherwise, leave this field blank and MettleCI will use the repository’s default branch (typically master or main).

   • In the Path field, enter ‘datastage’.

      

      

3. This page presents the same options as above, but for the Git repository holding your Compliance rules. Note that Compliance rules can be sourced from a subdirectory of your DataStage solution repository, if that’s how you want to organise your repositories.

    

    

   1. For example, the following configuration (using SSH URLs) would source compliance rules for ‘MYDATASTAGEPROJECT’ from a ‘compliance’ directory at the root of the DataStage Asset repository:

      1. DataStage Asset Repository configuration

         1. URL: ssh://git@bitbucket.org:datamigrators/mydatastageproject.git , Branch: , Path: ‘datastage’

      2. Compliance Repository configuration

         1. URL: ssh://git@bitbucket.org:datamigrators/mydatastageproject.git , Branch: , Path: ‘compliance’

             

4. Finally We need to select an Issue Management Service, if for now you are not interested in using a particular issue management system you can simply use the ‘Default Generic Issue Management’. If you have not yet configured your issue management system of choice see Using an Issue Management System.

When you’re done click Submit to register the project and return to the Registered Projects page.

Test the configuration of your registered project by…

1. running Compliance against a job and verifying that Workbench can read Compliance rules from the specified repository, and

2. making a trivial Job change (e.g. move an annotation a few pixels in any direction on the canvas) in the DataStage Classic Designer Client including saving and compiling your change) and then triggering a Git Commit process from the Workbench or custom menu item in the Designer Client.