From a30b999ea796273b94b1d7b8157ae4fa13a9efbc Mon Sep 17 00:00:00 2001
From: Harry Smith <hsmith@greshamtech.com>
Date: Wed, 4 Dec 2019 08:57:08 +0000
Subject: [PATCH] No Jira : alter building mechanism to be independent on
 Jenkins build numbers

---
 Jenkinsfile | 2 +-
 README.md   | 4 ++++
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/Jenkinsfile b/Jenkinsfile
index b39d30eab..098a130e6 100644
--- a/Jenkinsfile
+++ b/Jenkinsfile
@@ -23,7 +23,7 @@ pipeline {
                 branch "1.3.x"
             }
             steps {
-                sh "mvn versions:set -DnewVersion=1.3.3.GRESHAM-${env.BUILD_NUMBER}"
+                sh "mvn versions:set -DnewVersion=1.3.3.GRESHAM-18"
                 sh "mvn -N versions:update-child-modules"
 
                 timeout(time: 10, unit: 'MINUTES') {
diff --git a/README.md b/README.md
index 7b9646814..2c513b0a0 100644
--- a/README.md
+++ b/README.md
@@ -29,3 +29,7 @@ The authors and key contributors of the project include:
 
 
 Copyright &copy;2017, [MIT Internet Trust Consortium](http://www.trust.mit.edu/). Licensed under the Apache 2.0 license, for details see `LICENSE.txt`. 
+
+## Note for releasing
+
+Releases are made off of branch 1.3.x - the version released used to depend on the Jenkins build number but this is ineffective as the Jenkins history can vanish leaving you back at build number 1.  Therefore, in the Jenkinsfile, the version to be released needs altering on line 26 and incrementing by 1.