Release Process
- Ian Ibbotson (Use this one)
- Casey Henderson
dcb-service (Backend)
dcb-service is released from the main branch.
Ensure that the main branch is up to date.
Ensure tests pass and that there are no outstanding changes (Release will not progress)
When ready run
./gradlew cgTagFinal --withChangelog
git push --tags
git pushgithub will run the formal release process and upload all artefacts
dcb-locate
dcb-locate is released from the main branch.
Ensure that the main branch is up to date.
Ensure tests pass and that there are no outstanding changes (Release will not progress)
When ready run
./gradlew cgTagFinal --withChangelog
git push --tags
git pushgithub will run the formal release process and upload all artefacts
dcb-admin (Frontend)
dcb-admin is released by merging main onto to the release branch
git checkout main
git pull
git checkout release
git pull // Only needed if your local release branch is out-of-date.
git merge main
git pushgitlab actions will perform the release process uploading all artefacts. Once completed, we should merge release back on to main so that the latest version number is properly reflected in the dev env
We should also update the production branch with the latest changes from release. This ensures our production deployment at https://libraries-dcb-hub-admin-scaffold-uat-git-production-knowint.vercel.app/ stays current.
There is no need for any special handling for the Beta deployment at https://admin.ebscoqa.lsphost.com/ as this is based directly off the release branch.
However, the staging deployment does need to be updated individually, like so:
The staging deployment can be found at https://libraries-dcb-hub-admin-scaffold-uat-git-staging-knowint.vercel.app.
Operated as a Community Resource by the Open Library Foundation