...
| Step | Action | Results | Examples | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Go to latest Gerrit merged review of repo and comment 'stage-release' | ||||||||||
| 2 | Add and merge 'x.y.z.yaml' file to releases folder of the repository root. It describes the release and refers to maven-stage job previously ran. Set "tag_release: false" as we don't want to tag the repo at this step yet. This will be done at the next step. | Maven artifacts are published to maven release repository | |||||||||
| 3 | Add and merge 'x.y.z-container.yaml' file to releases folder of the repository root. It describes the release and refers to maven-docker-stage job previously ran. Set "ref" to the (full) SHA of the git commit to be tagged. Note. Might need Timestamp tag too. See
| Docker image is published to docker release repository | |||||||||
| 4 | Update OOM Update /kubernetes/cps/values.yaml in https://gerrit.onap.org/r/q/project:oom with new image versions | ||||||||||
| 5 | Prepare the next release by bumping and merging new version numbers:
| Repo is ready for next release |
|
...