Enable Git Signing

Git commit signing is enabled for your entire MettleCI Workbench instance, after which it is made available to those users who configure their Workbench user profile appropriately. To enable Git commit signing in your Workbench instance set the commitSigningEnabled to true in your config.yml file. See MettleCI Workbench Configuration Files Explained - gitAuthentication for an example.

Git commits can now be signed by those users who have uploaded a GPG key in their profile (ask Drew for screenshot)

Users who have not uploaded a private GPG to their Workbench profile will continue to be able to commit to their authorised repositories, however their commits will remain unsigned until they provide Workbench with an appropriate key.

Configure User Profiles

Create a GPG key at command line

Upload the private key to workbench and the public key to their account in Github/Gitlab

Commits are now signed!

When your DataStage Password Changes

When a user’s DataStage password changes their GPG (Workbench) key will need to be re-encrypted by Workbench using this new password.

To do this a user will need to re-upload their original GPG key to Workbench. If they choose to use a new private GPG key with Workbench they’ll also need to upload the new public key to their Git platform.

Any user whose DataStage password has changed will, until they re-uploaded their private GPG to Workbench, be presented with the following error during Workbench Commit operations:

Cannot retrieve git signing key because your DataStage password has changed. Please re-upload your signing key and try again.