-
Notifications
You must be signed in to change notification settings - Fork 49
Release Process
Jonathan Percival edited this page Mar 1, 2022
·
1 revision
Merges to master trigger a deployment to the Maven Snapshots repositories.
Once ready for a release, the master branch is updated with the correct version number and is tagged.
Tags trigger a full release to Maven Central and a corresponding release to Github.
Releases SHALL NOT have a SNAPSHOT version, nor any SNAPSHOT dependencies.
To release a new version of CQF Ruler:
- Ensure target versions/releases of:
- HAPI
- CQFTooling
- CDSHooks
- Update master to be a release (i.e. no SNAPSHOT) version
- Regression test each of the operations of all the plugins
- Passed Travis Build for release profile
- Create a Github Release (which creates a tag at the current commit of master)
- Choose the "Auto-generate release notes" option
- Travis does the release to Maven, ensure binaries are published to the binaries repository:
- Travis does the release of the image to DockerHub
- Ensure the image is published to DockerHub (https://hub.docker.com/r/alphora/cqf-ruler)
- Update master to vNext-SNAPSHOT
- Ensure all issues included in the release are Closed