...
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 updThe following steps are important when you release an individual component. These steps also update the serviceVersion of that component, the other items below need to change.
These steps apply when you change its a component's 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 -SNAPSHOT this component is working towards.
- 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."
- 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/
- See 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 openlmis-contract-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.