Consumed API from other projects
| Project | API Dependency | Notes |
|---|---|---|
| Portal | 2.1.0 | When portal team releases we will upgrade. |
| AAF | v1.0.0 - ?? | Waiting for AAF team to release their artifacts |
| Dmaap | v1.1.3 | |
| AAI | v11 | No direct link to any libraries |
| APP-C | No direct link to any libraries | |
| SO | No direct link to any libraries | |
| VFC | No direct link to any libraries |
Published API - These projects use the policy libraries to build their code
| Project | API | Notes |
|---|---|---|
| CLAMP | 1.2.0 | |
| DCAE | n/a | Implemented own python API |
1. Follow the process as outlined here: Independent Versioning and Release Process. Policy repositories inherit from oparent so release jobs will fail if any SNAPSHOT artifact is referenced in the pom.xml's.
- Verify there are no SNAPSHOTs and we are up-to-date with other team's released artifacts.
- Send Helpdesk tickets to LF ONAP release engineering specifying the Jenkin's Job to release Java artifacts and then the docker images
- Update the Integration team manifest so public knows what released artifacts are available. Example gerrit review:
- Update the Demo team heat scripts so the automated External Lab Jobs work and the Integration team has the latest artifacts for testing. Example gerrit review:
- TODO: Update the OOM team K8S Helm Charts ???
2. For any new changes to be done post-Release. Then the we must update to the next SNAPSHOT version:
| Repo | Notes | Example Commit(s) |
|---|---|---|
| policy/common | all pom.xml's version.properties | https://gerrit.onap.org/r/#/c/28107/ |
| policy/drools-applications | all pom.xml's version.properties | |
| policy/drools-pdp | all pom.xml's version.properties | |
| policy/engine | all pom.xml's version.properties BRMSGateway/config.properties BRMSGateway/dependency.json BRMSGateway/src/main/java/org/onap/policy/brmsInterface/BRMSPush.java BRMSGateway/src/test/resources/config.properties | |
| policy/docker | all pom.xml's version.properties config/pe/brmsgw.conf | https://gerrit.onap.org/r/#/c/28185/ |
When branching, its easiest to update the .gitreview file ON the new branch in order to ensure that new gerritt submissions are tracked on that branch.
If this is not done, then one should specify the branch when submitting the git review. 'git review beijing'
[gerrit] host=gerrit.onap.org port=29418 project=policy/engine.git defaultbranch=beijing