Git Changelog

Git Changelog Plugin

Build Status

Creates a changelog, or release notes, based on Git commits between 2 revisions.

This can also be done with a command line tool.


You can use this plugin either in a pipeline or as a post-build action.

There is a complete running example available here:


The plugin is compatible with the pipeline plugin and can be configured to support many use cases. You probably want to adjust it using the Snippet Generator.

The gitChangelog step can return:

  • Context - An object that contains all the information needed to create a changelog. Can be used to gather information from Git like committers, emails, issues and much more.
  • String - A string that is a rendered changelog, ready to be published. Can be used to publish on build summary page, on a wiki, emailed and much more.

The template and context is documented here.

It can integrate with issue management systems to get titles of issues and links. You will probably want to avoid specifying credentials in plain text in your script. One way of doing that is using the credentials binding plugin. The supported integrations are:

  • GitLab
  • GitHub
  • Jira

You can create a file or maybe publish the changelog with:

You can filter out a subset of the commits by:

  • Specifying specific from/to references/commits.
  • Adding filter based on message.
  • Adding filter based on commit time.
  • Filter tags based on tag name.
  • Filter commits based on commit time.
  • Ignore commits that does not contain an issue.

You can make the changelog prettier by:

  • Transforming tag name to something more readable.
  • Changing date display format.
  • Creating virtual tag, that contains all commits that does not belong to any other tag. This can be named something like Unreleased.
  • Creating virtual issue, that contains all commits that does not belong to any other issue.
  • Remove issue from commit message. This can be named something like Wall of shame and list all committers that did not commit on an issue.

Check the Snippet Generator to see all features!

Pipeline with context

Here is an example that clones a repo, gathers all jiras and adds a link to jira in the description of the job. The context contains much more then this and is documented here.

node {
 sh """
 git clone .

 def changelogContext = gitChangelog returnType: 'CONTEXT',
  from: [type: 'REF', value: 'git-changelog-1.50'],
  to: [type: 'REF', value: 'master'],
  jira: [issuePattern: 'JENKINS-([0-9]+)\\b', password: '', server: '', username: '']

 Set<String> issueIdentifiers = new TreeSet<>()
 changelogContext.issues.each { issue ->
  if ( == 'Jira') {
 currentBuild.description = "${issueIdentifiers.join(',')}%29"

Pipeline with string

Here is an example that clones a repo and publishes the changelog on job page. The template and context is documented here.

node {
 sh """
 git clone .

 def changelogString = gitChangelog returnType: 'STRING',
  from: [type: 'REF', value: 'git-changelog-1.50'],
  to: [type: 'REF', value: 'master'],
  template: """
  // Template is documented below!

 currentBuild.description = changelogString

Determine next version from commit messages

By giving the plugin patterns, to match against commits, it can calculate next semantic version to use. This can be part of a release-pipeline, to automate version stepping. It will find the previous highest semantic Git tag and step it depending of matched patterns.

def nextVersion = getNextSemanticVersion()
println "Next version:" + nextVersion.toString();
println " Major:" + nextVersion.getMajor();
println " Minor:" + nextVersion.getMinor();
println " Patch:" + nextVersion.getPatch();

You can also specify custom regexp to match against commits:

def nextVersion = getNextSemanticVersion majorPattern: '^[Bb]reaking.*',
    minorPattern: '^[Ff]eature.*',
    patchPattern: '^[Ff]ix.*'

Determine highest version from commit messages

The plugin can find the previous highest semantic Git tag and provide major/minor/path numbers as well as the tag.

def highestVersion = getHighestSemanticVersion()
println "Highest version:" + highestVersion.toString();
println " Major:" + highestVersion.getMajor();
println " Minor:" + highestVersion.getMinor();
println " Patch:" + highestVersion.getPatch();
println " Git tag:" + highestVersion.findTag().orElse("");


The template and context is documented here.

Template - Simple

## {{name}}
### {{name}} [{{issue}}]({{link}}) {{title}} {{#hasIssueType}} *{{issueType}}* {{/hasIssueType}} {{#hasLabels}} {{#labels}} *{{.}}* {{/labels}} {{/hasLabels}}
### {{name}} {{issue}} {{title}} {{#hasIssueType}} *{{issueType}}* {{/hasIssueType}} {{#hasLabels}} {{#labels}} *{{.}}* {{/labels}} {{/hasLabels}}
### {{name}}


 * {{.}}

[{{hash}}]({{ownerName}}/{{repoName}}/commit/{{hash}}) {{authorName}} *{{commitTime}}*



Template - Semantic versioning from conventional commits

If you are using conventional commits:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

A changelog can be rendered (using Helpers) like this:

# Changelog

{{#ifReleaseTag .}}
## [{{name}}](https://gitservice/{{name}}) ({{tagDate .}})

  {{#ifContainsType commits type='feat'}}
### Features

      {{#ifCommitType . type='feat'}}
 - {{#eachCommitScope .}} **{{.}}** {{/eachCommitScope}} {{{commitDescription .}}} ([{{hash}}](https://gitservice/commit/{{hashFull}}))

  {{#ifContainsType commits type='fix'}}
### Bug Fixes

      {{#ifCommitType . type='fix'}}
 - {{#eachCommitScope .}} **{{.}}** {{/eachCommitScope}} {{{commitDescription .}}} ([{{hash}}](https://gitservice/commit/{{hashFull}}))


Post-build action

When the plugin is installed, it will add a new post build action in Jenkins job configuration.

Git Changelog

A couple of revisions are configured along with some other optional features. A editable template is available for the user to tweak.

Select references

The changelog is created from parsing Git and rendering the template with a context derived from the configured revisions.

Tweak template


This plugin can be built and started with maven and Jenkins' hpi plugin:


The functionality is implemented in git-changelog-lib. Pull requests are welcome!