You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Deliver Release Artifacts

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.

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  CPS-264 - Getting issue details... STATUS

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

Manage Release Branch

Prerequisites

  • Code is frozen at M3, no new development is made after M3
  • All testing (S3P, Integration Pair Wise) is completed at R0

Steps to create the release branch

  1. For R0, deliver releases artifacts from master branch as described in previous section.
  2. Create the release branch from Gerrit
  3. Increase pom version numbers
    1. In master branch, increase minor version number (if not already done)
    2. In release branch, increase patch version number
  4. In release branch, update ".gitreview " (change "defaultbranch" value)
  5. In ci-management repo, configure new Jenkins jobs for the release branch by adding a new release stream to the project.

Steps to deliver release patches

  1. Make the fix and have it merged in master branch
  2. From Gerrit, cherry pick the fix from master branch to release branch
  3. Once the fix is in release branch, deliver releases artifacts from release branch as described in previous section.

References

  • No labels