No Jira : alter building mechanism to be independent on Jenkins build numbers

pull/1601/head
Harry Smith 2019-12-04 08:57:08 +00:00
parent df84942311
commit a30b999ea7
2 changed files with 5 additions and 1 deletions

2
Jenkinsfile vendored
View File

@ -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') {

View File

@ -29,3 +29,7 @@ The authors and key contributors of the project include:
Copyright ©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.