Versions Compared

Old Version 36

changes.mady.by.user Niamh Core

Saved on

compared with

New Version 37

changes.mady.by.user Toine Siebelink

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.

Note. Might need Timestamp tag too. See 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-264

Docker image is published to docker release repository
  • Change 118178
  • Job cps-release-merge 2
4Update /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:

  • 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

...