Release Process

Owned by Ian Ibbotson (Use this one)
Last updated: Dec 19, 2024 by Casey Henderson
2 min read

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 origin main git push --tags

github 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 origin main git push --tags

github 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 push

gitlab 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 deployments from that branch.

We should also update the production branch with the latest changes from release. This ensures our MOBIUS 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 MOBIUS staging deployment does need to be updated individually, like so:

The MOBIUS staging deployment can be found at https://libraries-dcb-hub-admin-scaffold-uat-git-staging-knowint.vercel.app.

We should also update any other active environments listed in Confluence, such as the integration and GALILEO test environments https://openlibraryfoundation.atlassian.net/wiki/spaces/DCB/pages/2709585934 . The branches for all active DCB Admin deployments are marked as protected in GitLab.

GALILEO environments that must be updated as part of a release

Using the same protocol as above, we must also update these individual branches for our GALILEO deployments.

GALILEO_production

GALILEO_staging

GALILEO_test

Additional K-Int environments

It is also good practice to update VRTX-admin while we still have both AWS and VRTX DCB deployments for K-Int development environments.

Operated as a Community Resource by the Open Library Foundation