Skip to end of metadata
Go to start of metadata
  1. Increase version of poms and version.properties inside project.
  2. Merge code and run please release in gerrit to create new version of jars and images in nexus.
  3. Find the the last run for each of the following jenkins builds (for both Maven and Docker artifacts) that was on the version you want to release:
    1. <component>-master-docker-java-shell-daily
    2. <component>-master-release-version-java-daily
  4. Email helpdesk@onap.org with approval from PTL asking to release the version of those Jenkins jobs, so if job number 78 had the correct version then link those jobs
    1. https://jenkins.onap.org/view/<project>/job/<component>-master-release-version-java-daily/78/
    2. https://jenkins.onap.org/view/<project>/job/<component>-master-docker-java-shell-daily/78/
  5. Update version manifest files in integration repo to use newest versions. Files to update are
    1. integration/version-mainfest/src/main/resources/docker-mainfest.csv
    2. integration/version-mainfest/src/main/resources/docker-manifest-staging.csv
    3. integration/version-mainfest/src/main/resources/java-mainfest.csv
  6. Update the helm charts in OOM to point to newest versions of relevant projects.

Example:

To ensure promptly completion en releasing the Maven Artifacts and the Docker Artifacts you may want to use this table.


2 Comments

  1. For step 5, is it no longer necessary to update docker-manifest-staging.csv?


    1. Yes it is still necessary, making update to that now