Page Comparison

...

1. Create an SSH key pair at command line (guide here)

   1. This should be a user-specific key (i.e. not shared with other team members)

   2. Check with your Git platform’s documentation for the type of keys which are compatible with it.

2. Upload the private key to your MettleCI Workbench profile

   1. Click your avatar or user name in the top right-hand corner of the Workbench interface and select Profile.

   2. The Git Signing Key heading will have a

      Status
      colour Yellow title NOT SUPPLIED

      label next to it if you have not already supplied a key value. Select the Upload Key checkbox, paste your private SSH key into the text field and click Update Profile.
      

   3. When you upload your key to Workbench it encrypts it (using your DataStage password) and stores it safely in a Java key store (the same method used supporting to support accessing Workbench using HTTPS access). Once accepted the Git Signing Key heading will have a

      Status
      colour Green title SUPPLIED

      label next to it.
      

3. Upload the public key associated with your private SSH key to your account on your Git platform. See your Git platform’s instructions on how to achieve this.

4. Try performing a commit from MettleCI Workbench and check your Git platform to see if it’s recognised as a signed commit.

   1. Note that not all Git platforms have a visual indicator of a commit being signed. See your Git platform’s instructions on how to verify that a commit has been signed.

      

5. You can delete your private SSH key at any time by selecting the Delete Key checkbox and clicking the Delete Key button.

   

...