| Table of Contents |
|---|
Deliver Release Artifacts
...
| 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 git commit to be tagged. | Docker image is published to docker release repository | |
| 4 | Prepare the next release by bumping and merging new version numbers:
| 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
- For R0, deliver releases artifacts from master branch as described in previous section.
- Create the release branch from Gerrit
- Increase pom version numbers
- In master branch, increase minor version number (if not already done)
- In release branch, increase patch version number
- In release branch, update ".gitreview " (change "defaultbranch" value)
- 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
- Make the fix and have it merged in master branch
- From Gerrit, cherry pick the fix from master branch to release branch
- Once the fix is in release branch, deliver releases artifacts from release branch as described in previous section.