- Overview
- Reference Guide
- Setup & Architecture
- Release Notes
- API Reference
-
Integration Guides
-
Signing Capabilities
- Supported Formats and Platforms
- Timestamping
- Windows Signing - SignTool
- Apple Signing
- AppX & MSIX Signing
- Visual Studio ClickOnce
- Jar Signing
- Sign HLK/HCK using CodeSign Secure
- NuGet Signing
- Mage Signing
- Sign OVA/OVF using Encryption Consulting’s Utility Tool
- Utility Tool for code signing
- Container Signing
- PKCS11 Wrapper
- Reproducible Build
- CI/CD Integration
-
Signing Capabilities
Process Flow
Prerequisites for performing this task includes:
- A GitHub repository
- Signtool installed and configured
- ECSigning KSP installed and configured
- Jenkins Build Server and Project
To install and configure Signtool and the ECSigning KSP, please follow the steps mentioned here.
Before we get started, we will need to configure a Source Code Repository (i.e. GitHub). This version control system manages the commits for the builds pushed in the repository.
After configuring the source code repository, we will need to add a project on the Jenkins server to access the latest commit in the repository.
-
Sign into Jenkins
-
To create a new Pipeline, go to New Item from the sidebar
-
Enter the item name and select Pipeline from the list of services provided
-
Then the configuration tab will open to modify the settings of the project.
-
Enter the required details and information for the Pipeline. Here we are adding the String Parameters to convey the branch name of source code repository from which the latest builds will be accessed.
- Then we need to provide the Pipeline Script for the Reproducible Build.