Last Changes Plugin

The simplest way to know what has changed on your Jenkins builds!

Last Changes is a Jenkin plugin that shows rich VCS diffs between builds.

❗	Only Git and Svn based projects are supported.

Table of Contents

• 1. Introduction
• 2. Objectives
• 3. How it works?
• 4. Usage
• 5. Configuration
• 6. Docker

1. Introduction

The plugin uses diff2html to show last changes of a given build, example:

Or using side-by-side configuration:

ℹ️	Last changes means compare current revision with previous one.

2. Objectives

The main objective of this plugin is to have fast access to what has changed on a Jenkins build.

Another interesting aspect is that it can easily help to find the root cause of a failling build by highlighting what has changed.

And finally the plugin shines in a continuous delivery environment, where each commit generates a release candidate.

3. How it works?

1. This plugin expects git or svn based builds (a.k.a Source Code Management configuration section).

2. While your job runs the plugin reads your build workspace to retrieve the current VCS revision;

3. The diff between actual and previous revisions will be stored;

4. The diff for each build can be viewed later in html format.

❗	To get most from this plugin use periodically SCM pooling to trigger your builds, more details here.

⚠️	The plugin always compare current revision with previous one even no new commit has been made.

4. Usage

After installation just activate the post build action named Publish Last Changes.

1. Activate build action

   

2. Last changes menu should be available

   

3. Build changes history

   

4. Last changes menu is available for builds that published changes

   

5. Configuration

The setup is done via build configuration and basically reflects diff2html options:

6. Docker

An easy way to test this plugin is using a docker container, here are the steps (assumming you have docker installed):

1. Run the image:

   docker run -it -p 8080:8080 rmpestano/jenkins-last-changes

2. Access localhot:8080/ and create a job

3. Configure this svn repository: https://subversion.assembla.com/svn/cucumber-json-files/trunk/

4. Add the Publish last changes post build action;

5. Just run the job

Job output should look like: