How to manage Java certificates in a distributed Jenkins build environment?

I have a Jenkins server, which rotates nodes as the build traffic increases. I am trying to run integration tests with a project, and it requires me to have a certificate generated by keytool to connect to A safe system. (System configuration is as close as possible to prod, bonus! Out of my direct control).

How to add it to the system?

>If I manually put it on a node, I must know which node is running the test, and I must delete the file every time.
>If I check it into source control, Then it will be downloaded to the computer and unprotected in the workspace directory (if the job crashes, it cannot be deleted consistently)
>Downloading from the SSL site causes us to encounter the same problems as source control.
> p>

You can use the Copy To Slave plugin to automatically copy the keystore from the master server to the node. This happens when a job is started on a node as part of the workspace settings (so that it is available before the actual job starts executing). You can use it to copy the keystore into the workspace and reference it using a relative path.

I have a Jenkins server, and as the build traffic increases, it rotates the nodes. I am trying to run integration tests with a project, and it requires me to have a certificate generated by keytool to connect to A safe system. (System configuration is as close as possible to prod, bonus! Out of my direct control).

How to add it to the system?

>If I manually put it on a node, I must know which node is running the test, and I must delete the file every time.
>If I check it into source control, Then it will be downloaded to the computer and unprotected in the workspace directory (if the job crashes, it cannot be deleted consistently)
>Downloading from the SSL site causes us to encounter the same problems as source control.
> p>

You can use the Copy To Slave plugin to automatically copy the keystore from the master server to the node. This happens every time you start a job on the node, as Part of the workspace settings (so that it is available before the actual job starts executing). You can use it to copy the keystore into the workspace and reference it using a relative path.

Leave a Comment

Your email address will not be published.