Jenkins Integration for vcn
The integration has 3 main steps in what otherwise can be labeled a 10 step process. The 3 main steps are:
- Configuration System level
vcncredentials system-wide in Jenkins
- Per build job
vcncredentials in from system configuration to local environment variables
- Sign asset
- Before deployment
vcn authenticatewith asset parameters
Step 1: System-level configuration
On the Home Screen, locate and click the Credentials link in the sidebar menu to expand the submenu beneath it.
With the submenu opened up, go ahead and select the credentials type, in this case, select System.
After selecting System, click Add Domain and notice the right-hand display shows ‘Global credentials (unrestricted)’. Click the link.
Create new credentials by selecting the Add Credentials option.
Step 2: Per build job
Now that you have the credential creation display opened, you will need to create your credential entries for your
vcn notarization password,
vcn user account, and
Once you have all 3, your list of credentials should look something similar to the below.
Next, you will need login and to configure the build job environment for each build job you have. This is relatively simple. All you need to do is to tie the
vcn credentials in from the system configuration to the local environment variables by setting the appropriate bindings.
After successfully setting your bindings, you will need to add a build job build step for signing your code with the
application. Click on the ‘Add build step’ drop down and select ‘Execute shell.’
vcn login and entering your credentials in the CLI, you will need to configure your build step for
vcn signing by typing in:
vcn login vcn notarize docker://gcr.io/vchain-ops/vcn:stable
…in the Command field.
Step 3: Before deployment
Lastly, you will need to execute this snippet in the deployment process:
~> vcn authenticate docker://gcr.io/vchain-ops/vcn:
stable && your_deploy_script.sh
And that’s it. You’re now ready to have vChain CodeNotary provide a perpetually running integrity check into all of your Jenkins build deployment pipeline, as well as ensure you are participating in the latest DevSecOps best practices.