Versions Compared

Old Version 42

changes.mady.by.user Rishi Chail

Saved on

compared with

New Version 43

changes.mady.by.user Rishi Chail

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

StepActionResultsExamples
1Go to latest Gerrit merged review of repo and comment 'stage-release'
  • maven-stage Jenkins job is triggered
  • maven-docker-stage Jenkins job is triggered
  • Maven artifacts are published to Nexus 2 autorelease repository
  • Docker images are published to Nexus 3 registry
  • Change 118168
  • Job maven-stage-master 109
  • Job maven-docker-stage-master 109


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.
This tag is NOT required for releases in H? (TBC)

Maven artifacts are published to maven release repository
  • Change 118174
  • Job cps-release-merge 1
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.


Take the latest built image, retag it without the timestamp :

e.g. SO release file

Code Block
container_release_tag: '1.1.0'
...
...
containers:
    - name: 'cps-and-ncmp'
      version: '1.1.0-SNAPSHOT-20210609T102555Z'


Docker image is published to docker release repository
  • Change 118178
  • Job cps-release-merge 2
4

Update https://gerrit.onap.org/r/q/project:oom with the release specific changes: 

  • Update /kubernetes/cps/values.yaml with new image versions
  • Update /kubernetes/cps/resources/config/application.yml if properties need to be added or updated.

Before pushing changes to the release-specific OOM branch, it is required to push them to master first. If it can not be done, then specify a reason in the release-specific change (for example, image version number is branch specific and it is expected that it could be different in master branch and release branch).



5

Prepare the next release by bumping and merging new version numbers:

  • In pom files, set to x.y.z-SNAPSHOT by running "mvn versions:set -DnewVersion=<snapshot version>"
  • In version.properties, set to x.y.z
Repo is ready for next release

...