Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Release all modules to be included in the maintenance distribution from CI, see releasing a module from bamboo and update the modules' releases in jira.
  2. Release the platform if necessary from bamboo, see platform release process.
  3. Create a maintenance branch off the latest released tag if it doesn't exist, forintsance if the current release of the reference application is 2.6 or 2.6.0, create a 2.6.x branch, below are the steps;
    • On the command line, navigate to the root of the distro project , the assumption is that you and run the commans below assumming you've already cloned the reference application distro project from git.

      Code Block
      git checkout -b new_branch_name tag_name
    • Change the version in the pom files in all the sub projects to a snapshot version e.g if the latest release is 2.6 or 2.6.0 and the branch name is 2.6.x, then the new version in the pom files would be 2.6.1-SNAPSHOT and commit the changes.

    • Then push the new branch out  to to origin and upstream.

  4. Release the distribution from CI
    1. Go to
    2. At the top of the page in the title section, there is a drop down to switch build branches, you need to set it to the branch you created above.
    3. You need to override the maven variables for the branch build, click the Actions button and select Configure branch from the drop down.At , at this point , you have the opportunity to set the plan variables , make sure you set below otherwise, maven release plugin will just use its default values;
      1. preparing.refapp.distro.release
       to true, the 
      1. : true
      2. maven.release.version
       and the
      1. : The maintenance version you intend to release
      2. maven.development.version: The next snapshot version in the pom
      files maven.development.version. Otherwise, maven release plugin will just use its default values, if you intend to package a later version
      1. files
      2. openMRSVersion: The version number of the platform
      1. you
      will need to change the value of the openMRSVersion variable too.
      1. intend to package
    4. To start the release process, you need to click the Run button from the build plan page, and select Run branch option from the drop down.
    5. Every build stops/pauses at the release stage (you can observe this in the left side column nearing the bottom of the page with section titled Release having a small right-arrow/play symbol beside it).
    6. After verifying Trigger the artifacts trigger the release by clicking on the play/right-arrow button next to the Release section located to the left bottomm bottom, this begins the process of releasing the OpenMRS 2.x version in maven and packaging the released modules and generating the
    7. After a successful Release, confirm that  preparing.refapp.distro.release bamboo variable is set to 'false'.
    8. Verify that the artifacts have been uploaded to sourceforge i.e the openmrs war file, read me file, the reference application standalone and modules zip files.
    9. Verify that has been updated to the latest released version and it runs correct modules.
    10. Verify that standalone, modules and war were correctly published at and work as expected.