Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

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 updating the version in the refapp distro.

 

 

 

(tick) Released with success

(error) Not yet tested

(question) partially released

(info) Release stage still in progress

 

For those modules, follow Releasing a Module from Bamboo. If you want to configure a new build to do the same, check Configuring a Plan to Release from Bamboo.

From your machine

If you are planning to release a new version of a module locally:

  • 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

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.)

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.

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.)

 

  • No labels