A Jenkins shared library to execute commands with vcn, our CLI tool

Learn how to reuse code in continuous integration pipelines with our digital assets attestation tool

If you need to use the same piece of code in many different pipelines, a Jenkins shared library is a good approach. After importing it, you will have access to its methods, which is a convenient way of avoiding repetition and improving scalability and maintainability.

Here at Codenotary we recently wrote a shared library with simple methods for some commands of our command line interface (CLI) tool, vcn, which we can then use on other pipelines in a very intuitive manner:

package lib

public class VCN implements Serializable {
    def context

    public VCN(def context) {
        this.context = context

    def execute(String command, String... arguments) {
        arguments = arguments.join(" ")
        context.echo context.sh(returnStdout: true, script: "./vcn ${command} ${arguments}").trim()

    def authenticate(String... arguments) {
        execute("authenticate", arguments)

    def bom(String... arguments) {
        execute("bom", arguments)

    def inspect(String... arguments) {
        execute("inspect", arguments)

    def list(String... arguments) {
        execute("list", arguments)

    def login(String... arguments) {
        execute("login", arguments)

    def logout(String... arguments) {
        execute("logout", arguments)

    def notarize(String... arguments) {
        execute("notarize", arguments)

    def serve(String... arguments) {
        execute("serve", arguments)

    def unsupport(String... arguments) {
        execute("unsupport", arguments)

    def untrust(String... arguments) {
        execute("untrust", arguments)

As you can see, the shared library exposes a class that models the vcn tool. When initialized, the class instance receives the Jenkins context, which allows it to execute the commands on the pipeline that called it. All methods representing the commands just receive any amount of String parameters and pass them, with the command name, to the execute method. The execute method then just joins the parameters received and calls vcn in a shell – with the command passed and the joined parameters.

This is an example Jenkins pipeline script that could make use of this shared library:

@Library('jenkins-libs@vcn') _

import lib.VCN

node('debian') {
    try {
	def vcn = new VCN(this)

	stage('Checkout vcn') {
	    checkout scm

	stage('Build vcn') {
	    sh "make"

	stage("Login") {
	    String arguments = "--lc-host ${LC_HOST} --lc-skip-tls-verify --lc-port 443"

	stage("Notarize vcn") {
            String arguments = '"*.py"'

	stage("Authenticate vcn") {
	    String arguments = 'vcn --output=""'

	} finally {
	    stage('Cleanup') {
	    step([$class: 'WsCleanup'])

The pipeline would work like this:

This is just a simple example to show the power of a Jenkins shared library. It can be certainly improved and extended to accommodate more robust needs required by a production environment.

You can try it yourself by starting a Codenotary Trustcenter trial:

CNIL Metrics & Logs

Self-Hosted performance monitoring and compliant log analysis for VMware vSphere, container and much more.


Built on the fastest immutable ledger technology. Open Source and easy to use and integrate into existing application.

Codenotary Cloud

Trusted CI/CD, SBOM and artifact
protection with cryptographic proof.
One CLI to manage all.

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials


Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).


immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance


Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.


While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace


No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data


IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.


immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence


CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.


As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.