Policy R3 Casablanca Independent Versioning And Release Process Plan
- Pamela Dragosh
- Liam Fallon
- Ram Krishna Verma
- Jorge Hernandez
Consumed API from other projects
Project | API Dependency | Notes |
|---|---|---|
Portal | 2.4.0 | |
AAF | v2.1.2 | |
Dmaap | v1.1.8 | |
SDC | 1.3.0 | |
AAI | v13 | 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.3.3 | Released on Nov 9, 2018 NOTE: For maintenance release on 1/2019 it is not required for CLAMP to upgrade to the >1.3.3 released artifacts. |
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. For Casablanca, the CI/CD daily release job does this by automatically failing if a SNAPSHOT is defined in the pom.xml's.
Send Helpdesk tickets to LF ONAP release engineering specifying the daily release CI/CD Job to officially release Java artifacts and any docker images generated by that release job. Eg. The LF moves from staging to the appropriate release repository.
Update the Integration team manifest so the community knows which released artifacts are available. Example gerrit review: https://gerrit.onap.org/r/#/c/42709/
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: https://gerrit.onap.org/r/#/c/42711/
If the branch has occurred, then we must also ensure the heat points to the correct branch: https://gerrit.onap.org/r/#/c/49869/1
Update the OOM team K8S Helm Charts. Example gerrit review: https://gerrit.onap.org/r/#/c/42713/
Note: If using maven version or release plugin, also manually check the versions are set correctly in the POMs, these plugins can miss POMs especially if they do not have Java source code in them.
2. For any new changes to be done post-Release. Then the we must update to the next SNAPSHOT version:
Release Order | Repo (current version) | Notes | Example Commit(s) for upgrading versions |
|---|---|---|---|
1 | policy/parent 2.0.1 | all pom.xml's version.properties | |
2 | policy/common 1.3.4 | all pom.xml's version.properties | |
3 | policy/drools-pdp 1.3.7 | all pom.xml's version.properties policy-management/src/test/resources/echo.pom In main pom.xml consider changing the policy.common.version property: *NOTE: The drools-pdp, drools-applications and engine must have the same version to support pre-loading of artifacts correctly. | |
3 | policy/apex-pdp 2.0.5 | all pom.xml's version.properties property version.policy.common in main pom.xml | |
4 | policy/drools-applications 1.3.7 | all pom.xml's version.properties In main pom.xml change the following properties
*NOTE: The drools-pdp and drools-applications must have the same version to support pre-loading of artifacts correctly. | |
5 | policy/engine 1.3.7 | all pom.xml's version.properties BRMSGateway/config.properties BRMSGateway/dependency.json BRMSGateway/src/main/java/org/onap/policy/brms/api/BrmsPush.java BRMSGateway/src/test/resources/config.properties In main pom.xml change the following properties
| https://gerrit.onap.org/r/#/c/71570/ |
6 | policy/distribution 2.0.6 | all pom.xml's version.properties In main pom.xml change the following properties
| |
7 (no dependencies, just ordering) | policy/docker (tagged 1.3.5) | There are no artifacts in this repo. But we need to be sure that any scripts that pull anything like templates are updated when branching. config/pe/push-policies.sh ./config/pe/brmsgw.conf: BRMS_DEPENDENCY_VERSION And it should be tagged by the LF release team to ensure consistency. |
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 casablanca'
[gerrit]
host=gerrit.onap.org
port=29418
project=policy/engine.git
defaultbranch=casablanca