The following instructions on running the Jenkins Pipeline assumes that EJBCA, SignServer, and Jenkins instances have been set up according to the instructions Prerequisites: Set up Instances.

Run Jenkins Pipeline

When making changes in Git, and pushing them with git stage and git commit, the pipeline is built automatically after a while, with a poll interval configured in Jenkins.

To trigger a build manually, forcing the pipeline to run even if nothing is changed, perform the following in the Jenkins Admin UI:

  1. Click Open Blue Ocean on the left to access Jenkins’s Blue Ocean interface.
  2. Click on the simple-java pipeline to view previous executions of the pipeline.
  3. Click Run to start the build, test, and deliver process.
  4. Click the running job to drill down on the output from the scripts.



The output shows the call to the SignServer SignClient and displays that the file is successfully signed using SignServer.