| Warning |
|---|
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:
| Code Block |
|---|
<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
...
| Note |
|---|
Check Configuring a Plan to Release from Bamboo to configure a new build to use this stage. |
| Warning | ||
|---|---|---|
| ||
Javadoc is failing for multiple modules. Read this thread before releasing a module, to make sure your module won't fail on javadoc generation.
If you accidentally tried to release a version and it failed in the release:perform due to that problem, you will need to release a new version. Do not try to reuse the same version as your first attempt. |
| Warning |
|---|
Got your release using JDK 7 instead of JDK 8? ''Unsupported major.minor version 52.0" Please set up JAVA_HOME variable for the release task as defined in Configuring a Plan to Release from Bamboo. |
When getting to the latest build of a module, the screen should be something like:
The default release version is defined in a variable named maven.release.version. The default next snapshot ( maven.development.version) is empty, and calculated by the maven release plugin.
You usually do not need to do this, but if you want to know what the next release will be (or if you want to change it), check the plan variables configuration:
When you click the 'play' button to kick the release, Bamboo will allow you to customise a few variables.
When you click the 'play' button to kick the release, Bamboo will allow you to customise variables - which will override the release number and the next .
You probably do not need to override anything.
| Note |
|---|
As per Versioning, you should use semver. The release scripts will return an error if you try something else. Also, if you are releasing 1.19.0, your next snapshot should be 1.20.0-SNAPSHOT, as per this discussion. If you don't override development version, it will be automatically set for you. |
If this module is part of the reference application, other option you might want to override is the global variable 'preparing.refapp.distro.release':
When it's true, the refapp distro will be updated with the released version; when it's false, with the next snapshot.
If the build goes red....
... read the logs. If it failed only to update the distro, it's possible to do it manually.
Other pages
| Child pages (Children Display) |
|---|
...