Skip to main content
This guide shows how to integrate Jenkins Code Signing with the KMES Series 3. This section provides useful terms, definitions, and concepts for this integration.

​
Jenkins terminology

A plugin implementsone or more build steps for consumption by a pipelineor project. By convention, though, a plugin generally implements only one build step to support separation. A pipelineis essentially a set of configurable build-steps. This terminology generally refers to the Pipeline plugin in general. A build stepis the fundamental building block of build automation in Jenkins. Everything that performs an action in your project is a build step. Everything, from pulling from Git to notifying users that a build is complete, is a build step. In relation, a stageis a logical grouping of those build steps. For example, you can skip the Test stage, but you must specify individual build steps to skip over. It also helps you visualize progress for consumers of the build results. Stages are not a required part of a pipeline and are strictly logical.

​
Pipeline scripting

Pipeline scripting comes in the following forms:
  • Declarative: A pre-defined set of tasks and environments in which to run build steps or Groovy expressions.
  • Imperative (or scripted): Similar to the declarative version, this form has some limitations because of the lack of a declarative environment. In exchange, you take advantage of the full power of Groovy. It’s very powerful but difficult to use.

​
FXCL Jenkins plugin

Without the FXCL Jenkins plugin, the existing Jenkins code signing plugins have no approval process. The resulting signature must be given immediately, or failure occurs. When you submit a request to sign, it fails because there is no time for approval to occur. There is also no way to query for the same request by using something like Jarsigner, which relies on PKCS11. The FXCL Jenkins Plugin accomplishes the following tasks:
  • Enables the standard approval process to take place by interfacing with the CryptoHub registration authority.
  • Enables you to sign files in bulk by incorporating FXCL functionality into the plugin.

​
Integration overview

This guide shows you how to perform the following tasks:
  1. Configure the KMES Series 3.
  2. Download and configure Jenkins and test the FXCL Jenkins plugin.
The following sections show you how to perform these tasks.