Consumed API from other projects
...
| Release Order | Repo (released version) | Notes | Example Commit(s) for upgrading versions |
|---|---|---|---|
| 1 | policy/parent 3.2.0 (TBD) | all pom.xml's version.properties | https://gerrit.onap.org/r/c/policy/parent/+/104021 |
| 2a | policy/docker 2.1.1 (TBD) | all pom.xml's version.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/c/policy/docker/+/102678 |
| 2b | policy/common 1.7.1 (TBD) | all pom.xml's version.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/c/policy/common/+/104047 |
| 3 | policy/models 2.3.5 (TBD) | all pom.xml's version.properties In main pom.xml change the following properties
| |
| 4a | policy/api 2.3.3 (TBD) | all pom.xml's version.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/c/policy/api/+/104257 |
| 4b | policy/pap 2.3.3 (TBD) | all pom.xml's version.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/c/policy/pap/+/104262 |
| 4c | policy/drools-pdp 1.7.4 (TBD) | all pom.xml's version.properties In main pom.xml consider changing the policy.common.version property:
Update policy/drools-applications dockerfile to pull this image (see below) Update policy/drools-applications files:
| |
| 4d | policy/apex-pdp 2.4.3 (TBD)4 | all pom.xml's version.properties In main pom.xml consider changing the policy.common.version property:
| |
| 4e | policy/xacml-pdp 2.3.3 (TBD) | all pom.xml's version.properties In main pom.xml consider changing the policy.common.version property:
| https://gerrit.onap.org/r/c/policy/xacml-pdp/+/104294 |
| 4f | policy/distribution 2.4.3 (TBD) | all pom.xml's version.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/c/policy/distribution/+/104296 |
| 5 - Dependent only on policy/drools-pdp | policy/drools-applications 1.7.4 (TBD)5 | all pom.xml's version.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/c/policy/drools-applications/+/104408 |
...
Steps for Releasing and branching |
|---|
Raise a review to refer released version of dependency (parent, common, models etc.) |
| Go to latest merged review of repo and comment “stage-release” |
It will trigger 2 Jenkins jobs - stage-master & docker-stage-master NOTE: The "docker-stage-master" job will fail for drools-applications |
Once the jobs are successful, create a yaml file for releasing maven artifacts first and raise a review. This file can typically be generated using this script: mkart.sh |
Once that is merged and build is successful, create another container.yaml file for releasing docker image and raise a review. This file can typically be generated using this script: mkdock.sh NOTE: Drools-applications will require a 2nd "stage-release" to be done due to the way it is built; the docker image requires the java artifacts to be released first, which are packaged into the image. |
| Once that is merged and build is successful, go to nexus3.onap.org & nexus.onap.org and verify that the image & artifacts were released |
Bump the snapshot version to next patch version and raise a review - Use this command “mvn versions:set -DnewVersion=<snapshot-version>” Update the patch version in "version.properties" file. |
| Below steps are ONLY needed when we are branching and proceeding to new release |
| Once that is merged and build is successful, go to gerrit and create a “guilin” branch. |
Once the branch is created, bump the master branch to next minor version using the same maven command and raise a review |
| Finally go to guilin branch and change the .gitreview file to point to guilin as default branch and raise the review. |