Conventional Commits

This plugin can be used to determine the next release version based on previous tags and the commit messages used.
It can also be used to get the current version. :warning: By default only annotated tag are supported, to support non annotated tag you must use an option to activate this feature (see below).:warning: It calculates the version number based on the format of the commit message.
The commit message format used is conventional commits.

This plugin can be used in a pipeline in a stage or the environment block. Some examples of this in use are:

pipeline {
    agent any

    environment {
        CURRENT_VERSION = currentVersion()
        NEXT_VERSION = nextVersion()
    }

    stages {
        stage('Hello') {
            steps {
                echo "current vesion = ${CURRENT_VERSION}"
                echo "next version = ${NEXT_VERSION}"
            }
        }
    }
}

def NEXT_VERSION
node {
    stage('Get next version ...') {
      CURRENT_VERSION=currentVersion()
      echo "Current version: $CURRENT_VERSION"  
      NEXT_VERSION=nextVersion()
      echo "Next version : $NEXT_VERSION"
    }
    stage ('Release') {
        sh "mvn release:prepare -DreleaseVersion=$NEXT_VERSION"
        sh 'mvn release:perform'
    }
}

The plugin provides provision to use optional parameters for support of build metadata, pre-release information, settings the start tag, etc. :warning: These parameters are only for the nextVersion step ! ⚠️

buildMetadata an optional parameter can be added as follows:

pipeline {
    agent any
    environment {
        NEXT_VERSION = nextVersion(buildMetadata: "$env.BUILD_NUMBER")
    }
    stages {
        stage('Hello') {
            steps {
                echo "next version = ${NEXT_VERSION}"
            }
        }
    }
}

Assuming next version is 1.1.0. The pipeline will output :next version = 1.1.0+001

For a 1.0.0 existing version the following code :

pipeline {
    agent any

    environment {
        NEXT_VERSION = nextVersion(preRelease: 'alpha')
    }

    stages {
        stage('Hello') {
            steps {
                echo "next version = ${NEXT_VERSION}"
            }
        }
    }
}

Will display :next version = 1.1.0-alpha

There are three options to manipulate the prerelease option :

• the name of the prerelease ➡️ preRelease
• keep the existing prerelease (default false) ➡️ preservePrelease
• increment the existing prerelease (default false) ➡️ incrementPreRelease

The table below resume the combined use of these options and the result:

The optional parameter writeVersion allow writing back to the file the next calculated version.

⚠️ For some configurations files, the CLI is needed (maven fo example). ⚠️

The supported configurations files :

• pom.xml (Maven) : need the Maven CLI in the path,
• package.json (NPM) : need the Npm CLI in the path,
• chart.yaml (Helm),
• build.gradle / gradle.properties (Gradle),
• setup.py / setup.cfg / pyproject.toml (Python),
• go.mod (GoLang).

Example of use : With a project with a package.json as follows :

{
  "name": "conventional-commits-plugin-example-npm",
  "version": "1.0.0",
  "description": "Npm example project"
}

The following pipeline with a commit with a commit message like feat: my cool feature:

pipeline {
    agent any
    environment {
        NEXT_VERSION = nextVersion(writeVersion: true)
    }
    stages {
        stage('Hello') {
            steps {
                echo "next version = ${NEXT_VERSION}"
            }
        }
    }
}

Will update the package.json as follows :

{
  "name": "conventional-commits-plugin-example-npm",
  "version": "1.1.0",
  "description": "Npm example project"
}

Report issues and enhancements in the Github issue tracker.

We encourage community contributions for this project! For more information on how to contribute to this project, see the contribution guidelines

Licensed under MIT, see LICENSE