...
Once all these steps are completed and verified, the release process is complete. At this point you can conduct communication tasks such as sharing the URL and Release Announcement to stakeholders. Congratulations!
...
Updating a Component ServiceVersion
Each component is always working towards some future release, version X.Y.Z-SNAPSHOT. A component may change what version it is working towards, and when you upd
The following steps are important when you release an individual component. These steps also apply when you change its serviceVersion (changing which -SNAPSHOT the codebase is working towards).
- Within the component, set the serviceVersion property in the gradle.properties file to the new -SNAPSHOT you've chosen.
- See Step 3 above for details.
- Update openlmis-ref-distro to set docker-compose.yml to use the new release version or the new -SNAPSHOT this component is working towards
See the lines under "services:" → serviceName → "image: openlmis/requisition-refui:3.0.0-beta-SNAPSHOT" and change that last part to the new version tag or snapshot tag for the service.- See Step 5 above for details.
- Use a commit message that explains your change. EG, "Upgrade to 3.1.0-SNAPSHOT of openlmis-requisition component."
- Commit this change.
- IF you are doing an entire release of the whole openlmis-ref-distro at this time, you would tag the openlmis-ref-distro repo with the release being made (see instructions above).
- Update openlmis-deployment to set each docker-compose.yml file in the deployment/ folder for the relevant environments, probably uat_env/, test_env/, but not demo_env/
- For the component/service you are updating, change its version to the release or snapshotSee Step 7 above for details.
- Similar to above, please include a helpful commit message. (You do not need to tag this repo because it is only used by Jenkins, not external users.)
- Update Update openlmis-contract tests TBD-tests to set each docker-compose.*.yml file that includes your component to use the new -SNAPSHOT version.
- Similar to the steps above, see the lines under "services:" and change its version to the new snapshot.
- You do not need to tag this repo. It will be used by Jenkins for subsequent contract test runs.