It would help a lot if a release can be built and published by just pushing to the release branch. Here the corresponding script should perform following steps:
verify the pushed commit has already been built and successfully tested in the master branch. Otherwise fail.
read the revision value from the top level pom.xml
run the build without tests using the release profile and by setting the revision parameter to the read value from 2 without the -SNAPSHOT suffix.
If the build is successful, tag it using the value from 2 with v prefix and without the -SNAPSHOT suffix. Otherwise fail.
Increment the minor version in the value from 2 and update the revision property in the pom.xml.
Commit the change
Push all changes (commit from 6 and tag from 4) to the origin master.
It would help a lot if a release can be built and published by just pushing to the release branch. Here the corresponding script should perform following steps:
revisionvalue from the top levelpom.xmlreleaseprofile and by setting therevisionparameter to the read value from 2 without the-SNAPSHOTsuffix.vprefix and without the-SNAPSHOTsuffix. Otherwise fail.revisionproperty in thepom.xml.