Versions Compared

Version Old Version 16 New Version 17
Changes made by

Larry Pieniazek

Larry Pieniazek

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Create a blank GitLab project by selecting new project from your GitLab dashboard, or visiting http://your.gitlab.server/projects/new. The recommended practice is to create a new GitLab project for each DataStage project, plus one for your compliance rules. You may want to collect your GitLab projects into groups. See GitLab - Create Project.

    Image Removed

    Clone the empty repository to somewhere convenient, such as your local client machine. Create a README file which ensures the Git repository is initialized, has a default branch, and can be cloned. A sample README file is supplied in the template repository supplied with MettleCI.

  2. For integration with MettleCI Workbench, with CI/CD pipelines, and with external entities in general, you will need to set up access to the repository associated with the project

    1. Decide what access style you will use, userid/password, userid/PAT, deploy keys or SSH (we recommend SSH, see Configuring MettleCI Workbench SSH Authentication to GitLab for more details)

    2. Create a public/private key pair and then add it to the project. SeeAdding public keys to GitLab for more details

  3. Set up access between GitLab and the MettleCI Workbench service (typically running on your DataStage Engine host)

    1. Obtain the “clone URL” for the project

    2. Configure the project in MettleCI Workbench. See MettleCI Workbench Configure First Project for more details.

    3. Test this setup by using MettleCI Workbench to run a compliance check (this tests read only access to Compliance) and perform a commit (this tests write access to the Project repository)

  4. Set up access between GitLab and your build server. The easiest way to do this is to create a (project-specific or public) deploy key. Public keys can be used across multiple GitLab projects, once the project administrator grants access, while private keys only grant access to one project. (What do I do with this key, Larry Pieniazek (Unlicensed) ?)

    1. This page, while targeted at MettleCI Workbench setup, also covers how to create Deploy keys (Configuring MettleCI Workbench SSH Authentication to GitLab )

    2. Pipelines use a .gitab-ci.yml file to hold configuration information.

    3. How?

  5. How do we test it?

...