We want the deployment scripts that Jenkins runs to be able to deploy the 3.0 Beta tag to the UAT environment (uat.openlmis.org). We also want to be able to set it to deploy a different release tag in the future (eg, '3.0.0-rc1', '3.2.1', etc).
We think the best approach is where the jenkins job is a parameterized build, where the parameter is the release we want to deploy. Take the parameter, use it to checkout a corresponding tag in openlmis-deployment which has the form of the compose file we want to release.
We can provide a release tag name and push a button in Jenkins to have it build and deploy that specific version to the UAT environment. Document in this ticket how this process will work.
Implement this into our Jenkins setup at build.openlmis.org and our deployment scripts.
Update the CI/CD documentation in the wiki.
Update the Rolling a Release wiki page.