Release job: Avoid auto-release when there are no "releasable" commits

The determination of "releasable" is in the release scripts, but
currently it boils down to having an issue key in the commit message.

Author: yrodiere

ci/release/Jenkinsfile

@@ -122,14 +122,15 @@ pipeline {
 					else {
 						echo "Release was triggered automatically"
 
-						// Avoid doing an automatic release for commits from a release
-						def lastCommitter = sh(script: 'git show -s --format=\'%an\'', returnStdout: true).trim()
-						def secondLastCommitter = sh(script: 'git show -s --format=\'%an\' HEAD~1', returnStdout: true).trim()
-						echo "Last two commits were performed by '${lastCommitter}'/'${secondLastCommitter}'."
-
-						if (lastCommitter == 'Hibernate-CI' && secondLastCommitter == 'Hibernate-CI') {
-							print "INFO: Automatic release skipped because last commits were for the previous release"
-							currentBuild.result = 'ABORTED'
+						// Avoid doing an automatic release if there are no "releasable" commits since the last release (see release scripts for determination)
+						def releasableCommitCount = sh(
+								script: ".release/scripts/count-releasable-commits.sh ${env.PROJECT}",
+								returnStdout: true
+						).trim().toInteger()
+						if ( releasableCommitCount <= 0 ) {
+							print "INFO: Automatic release skipped because no releasable commits were pushed since the previous release"
+							currentBuild.getRawBuild().getExecutor().interrupt(Result.NOT_BUILT)
+							sleep(1)   // Interrupt is not blocking and does not take effect immediately.
 							return
 						}