The maven release plugin assumes you are releasing from the latest commit on the current branch (HEAD). You cannot release from a previous build, it has to be the latest one.
Before running the build, it's possible to customise the versions:
It's possible to change the next released version in the Plan Configuration as well:
Configuring a plan to have a release step:
1) Change the SCM tag of your pom file to SSH. Example:
<scm>
<connection>scm:git:git@github.com:openmrs/openmrs-module-allergyapi.git</connection>
<developerConnection>scm:git:git@github.com:openmrs/openmrs-module-allergyapi.git</developerConnection>
<url>https://github.com/openmrs/openmrs-module-allergyapi.git</url>
</scm>
2) Create the plan variables:
- maven.development.version - leave it empty. It could be used to override the default value
- maven.release.version: add the next release version of this module. Check the pom file in doubt.
- refapp.distro.property: only necessary if this module is part of the refapp distro. The maven property in the refapp distro pom file for this module.
3) In the plan configuration, add 'Release scripts' as the second repository:
4) Remove the polling trigger of the 'Release scripts' repository
6) Copy the release job from Allergy API, into a manual stage
* clean checkout
Other pages