Consumed API from other projects
| Project | API Dependency | Notes | |
|---|---|---|---|
| AAF | v2.1.21 | ||
| Dmaap | v1.1.11 | ||
| SDC | 1.6.5 - sdc-tosca 1.4.1 - sdc-distribution-client | ||
| AAI | aai-schema 1.7.2 | ||
| SO | REST - No direct link to any libraries | ||
| VFC | REST - No direct link to any libraries | ||
| SDNR | Dmaap - No direct link to any libraries | ||
| SDNC | REST - No direct link to any libraries | ||
| CDS | 0.4.4 | TODO1.1.5 | GRPC <groupId>org.onap.ccsdk.cds.blueprintsprocessor</groupId> |
Published API - These projects use the policy libraries to build their code
...
| Release Order | Repo (released version) | Notes | Example Commit(s) for upgrading versions |
|---|---|---|---|
| 1 | policy/parent 3.3.13 | all pom.xml's version.properties | |
| 2a | policy/docker 2.2.1 | all pom.xml's version.properties In main pom.xml change the following properties
Update Dockerfile in all repos with new version | https://gerrit.onap.org/r/c/policy/docker/+/114316 |
| 2b | policy/common 1.8.13 | all pom.xml's version.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/c/policy/common/+/114285 |
| 3 | policy/models 2.4.35 | all pom.xml's version.properties In main pom.xml change the following properties
| |
| 4a | policy/api 2.4.25 | all pom.xml's version.properties In main pom.xml change the following properties
In Dockerfile
| https://gerrit.onap.org/r/c/policy/api/+/119672 |
| 4b | policy/pap 2.4.26 | all pom.xml's version.properties In main pom.xml change the following properties
In Dockerfile
| https://gerrit.onap.org/r/c/policy/pap/+/114290 |
| 4c | policy/drools-pdp 1.8.35 | all pom.xml's version.properties In main pom.xml consider changing the policy.common.version property:
In Dockerfile
Update policy/drools-applications dockerfile to pull this image (see below) Update policy/drools-applications files:
| |
| 4d | policy/apex-pdp 2.5.25 | all pom.xml's version.properties In main pom.xml consider changing the policy.common.version property:
In Dockerfile
| https://gerrit.onap.org/r/c/policy/apex-pdp/+/114292 |
| 4e | policy/xacml-pdp 2.4.36 | all pom.xml's version.properties In main pom.xml consider changing the policy.common.version property:
In Dockerfile
| https://gerrit.onap.org/r/c/policy/xacml-pdp/+/122180 |
| 4f | policy/distribution 2.5.25 | all pom.xml's version.properties In main pom.xml change the following properties
In Dockerfile
| https://gerrit.onap.org/r/c/policy/distribution/+/114291 |
| 4g | policy/clamp 6.0.2 | all pom.xml's version.properties In main pom.xml change the following properties
In Dockerfile
| https://gerrit.onap.org/r/c/policy/clamp/+/118101 |
| 5 - Dependent only on policy/drools-pdp | policy/drools-applications 1.8.35 | all pom.xml's version.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/c/policy/drools-applications/+/114862 |
...
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 “honolulu” branch. |
Once the branch is created, bump the master branch to next minor version using the same maven command, update the dependencies to the new SNAPSHOT versions, and raise a review |
| Finally go to honolulu branch and change the .gitreview file to point to honolulu as default branch and raise the review. |