Maven Artifact versioning and Docker image versioning are independent process.
Maven Artifact version
Files that needs to be changed
- <project>/pom.xml (eg. has/pom.xml)
- Conductor has an additional pom: has/conductor/pom.xml
- Watch for oparent-python version changes. This should be mapped to release version of oparent-python.
Process to follow to release maven artifacts to release repository (needed when pom.xml version changed)
- Jenkins verify/merge stage master jobs create snapshot and staging artifacts.
- https://nexus.onap.org/content/repositories/snapshots/org/onap/optf/
- https://nexus.onap.org/content/repositories/staging/org/onap/optf/
- Once patch merged run "please release" and note the Jenkins release job number.
- Raise a ONAP helpdesk ticket to request release of maven artifacts.
- Once acknowledged, verify if the correct version of artifacts that was released exists in the following path.
https://nexus.onap.org/content/repositories/releases/org/onap/optf/
Docker versioning
Files that needs to be changed
- has<project>/version.properties (eg osdf/version.properties)
...
- <project>/run-dockers.sh
Process to follow to release docker images
- run Run "please release". Two separate jenkins jobs will create SNAPSHOT-${TIMESTAMP}, SNAPSHOT-latest, STAGING-${TIMESTAMP}, STAGING-latest image tags
- Raise a ONAP helpdesk ticket to request release of Docker images.
- Vrify Verify the version timestamp etc in https://nexus3.onap.org/#browse/search=keyword%3Doptf
OOM, CSIT, HEAT, INTEGRATION project updates
- Update docker manifest for RELEASE and STAGING in integration project
- Update OOM, HEAT projects
- Update CSIT repo with the new versions