Deploying to maven
From Bamboo
Some modules already have a 'release' stage on their build. This stage is responsible for doing the release prepare/perform, and update the version in the refapp distro.
| Expand | ||
|---|---|---|
| ||
|
From your machine
If you are planning to release a new version of a module locally:
- Get privileges to deploy release artifacts to mavenrepo.openmrs.org
- Actually release the module, using
mvn release:prepare release:perform - more in Maven Release Process
- If the reference application includes the latest a snapshot of this module (you can check here) then update openmrs-distro-referenceapplication/pom.xml to refer to the (new) latest snapshot
| Expand | ||
|---|---|---|
| ||
Releasing a Module from Bamboo Should the referenceapplication have latest? |
...
Uploading the omod to modules.openmrs.org
...
...
The steps you ran above with the mvn release plugin will have created your official module-x.y.omod file under omod/target, and deployed this to our maven repository so that developers can access it programmatically. For implementers to be able to access it manually, you need to upload it to the Module Repository. (You can log in using your OpenMRS ID.)
| Expand | ||
|---|---|---|
| ||
Using a REST call to modules.openmrs.org |
If you used Bamboo, it need to retrieve the omod from nexus
Update the JIRA project
Release the version in JIRA, and create the next fixVersion.
| Expand | ||
|---|---|---|
| ||
Using a REST call to JIRA |
Inform about the release
If this module is part of the reference application (check here), especially if it includes a snapshot version, then email the dev-refapp mailing list so that other interested parties know to upgrade their distros (Mirebalais, Bahmni, etc.)
...
| title | Possible automation... |
|---|
...