...
- Find the Jenkins stage job that created the release candidate.
- Go to Jenkins and select the tab for the product to release.
- Find the link for the "<product>-maven-stage-master" job and click it.
- From the list of jobs, find the number for the job that created the artifact to release, the date of the run can be of help here.
- Put the number at the end of the "log_dir" value seen in the example below.
- Alternative way to find Jenkins stage job.
- Look among its output logs for the file with the name: staging-repo.txt.gz, it will have a URL like this:
- https://logs.acumos.org/production/vex-yul-acumos-jenkins-1/common-dataservice-maven-dl-stage-master/4/staging-repo.txt.gz
- Create a new/update existing release yaml file in the directory "releases/" at the repo root.
- The file name should be anything, but most projects use a pattern like "release-maven.yaml". An example of the content appears below.
- The file content has the project name, the version to release, and the log directory you found above, altho in abbreviated form.
- Create a new change set with just the new file, commit to git locally and submit the change set to Gerrit.
- After the verify job succeeds, a project committer should merge the change set. This will tag the repository with the version string AND release the artifact.
...