Project-Files-Signing

This guide explains how to configure the necessary variables and secure files for the Code Signing process in your pipeline.

Assigning the Necessary Variables

In the Pipeline Library, there is:

• A variable group called Code Signing
• Two secure files:
  • client_certificate.p12
  • signtool.exe
  

You’ll need to link the variable group to your pipeline.

Linking the Variable Group

1. Go to Pipelines and open your desired pipeline.
2. Click Edit in the top right corner
3. Click the three dots (⋯) in the top-right, then select Triggers
4. Open the Variables tab, then go to Variable Groups. Click Link variable group.
5. In the right-hand panel, search for Code Signing, select it, and click Link

You have now successfully linked the required variables for the Code Signing process.

Secure Files

Note: Every pipeline automatically has access to the designated secure files. These steps are only necessary if access is missing or needs to be configured manually.

1. Go to the Pipeline Library and access the secure files tab.
2. Click on the client_certificate.p12
3. On the top click on Pipeline permissions
4. In this dialog click on +, search your Pipeline and click on it
5. If you want to enable open access (every pipeline can access this file, then press the 3 dots next to the + and click on open access

Now everything should be working and you can insert the Code Signing steps from the templates into your Pipeline.

Important Notes

• If your project includes scripts that execute independently (not copied in by another process), those scripts must be signed.
• If this is not the case, use the MSI signing template instead.
• We have a limited number of available signatures, so please use them wisely.