Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We have also created a JIRA called POLICY-112911 to cover the task of performing the release.

Phase 1: Update references in policy/parent

...


Get the release data.

Note

Note that the The -l parameter is pointing to the location of the checked out Policy Framework repositories (onap/policy/parent, onap/policy/common etc) and -b specifies the branch to sue for the release. If the -b option is not specified, the master branch is used.

...

Perform Phase 1, update of references in policy/parent

Code Block
languagebash
 % releasePhase.sh -l onap -i POLICY-112911 -p 1
Updating parent references in the parent pom and generating commit . . .
updating policy parent reference to 3.5.5 on onap/policy/parent . . .
policy parent reference updated on onap/policy/parent
generating commit 'update parent references in policy/parent pom' . . .
[jakarta ae6cc59] update parent references in policy/parent pom
 1 file changed, 1 insertion(+), 1 deletion(-)
commit 'update parent references in policy/parent pom' generated
sending commit 'update parent references in policy/parent pom' to gerrit . . .
remote: 
remote: Processing changes: refs: 1, new: 1        
remote: Processing changes: refs: 1, new: 1        
remote: Processing changes: refs: 1, new: 1        
remote: Processing changes: refs: 1, new: 1, done            
remote: 
remote: SUCCESS        
remote: 
remote:   https://gerrit.onap.org/c/onap/policy/parent/+/15332 update parent references in policy/parent pom [NEW]        
remote: 
To ssh://gerrit.nordixonap.org:29418/onap/policy/parent
 * [new reference]   HEAD -> refs/for/jakarta
commit 'update parent references in policy/parent pom' sent to gerrit . . .
Updated parent references in the parent pom and generated commit

The references are updated in the local repositories and a commit is created in Gerrit for the change.

The commit is reviewed and merged as normal.

Phase 2: Release policy/parent

When the commit for Phase 1 has been merged and the merge job has completed, stage the release of the policy/parent Maven artifacts by giving the stage-release magic word as a comment on the release commit. When the stage release job has completed in Gerrit, you can proceed to run Phase 2.

Get the release data.

Note

The output from git on the getReleaseData.sh script is omitted from Phase 2 for brevity.


Code Block
languagebash
% getReleaseData.sh -l onap -b jakarta
Repo, Last Tag Version,Snapshot Version,Changed Files,Docker Images
policy/parent,3.5.4,3.5.5-SNAPSHOT,1,
policy/docker,2.4.4,2.4.5-SNAPSHOT,85,'policy-jre-alpine':'policy-jdk-alpine':'policy-db-migrator'
policy/common,1.10.4,1.10.5-SNAPSHOT,0,
policy/models,2.6.5,2.6.6-SNAPSHOT,2,'policy-models-simulator'
policy/api,2.6.4,2.6.5-SNAPSHOT,1,'policy-api'
policy/pap,2.6.4,2.6.5-SNAPSHOT,1,'policy-pap'
policy/apex-pdp,2.7.4,2.7.5-SNAPSHOT,1,'policy-apex-pdp'
policy/drools-pdp,1.10.4,1.10.5-SNAPSHOT,1,'policy-drools'
policy/xacml-pdp,2.6.4,2.6.5-SNAPSHOT,1,'policy-xacml-pdp'
policy/distribution,2.7.4,2.7.5-SNAPSHOT,1,'policy-distribution'
policy/clamp,6.2.4,6.2.5-SNAPSHOT,8,'policy-clamp-backend':'policy-clamp-ac-pf-ppnt':'policy-clamp-ac-k8s-ppnt':'policy-clamp-ac-http-ppnt':'policy-clamp-runtime-acm'
policy/gui,2.2.4,2.2.5-SNAPSHOT,2,'policy-gui'
policy/drools-applications,1.10.4,1.10.5-SNAPSHOT,6,'policy-pdpd-cl'

Perform Phase 2, release policy/parent

Code Block
languagebash
% releasePhase.sh -l onap -i POLICY-112911 -p 2
Generating artifact release yaml file and commit for policy/parent . . .
have you run 'stage-release' on the 'policy/parent' repo? y
Branch: jakarta
Project: policy/parent
Version: 3.5.5
Stage ID: policy-parent-maven-stage-jakarta/145/
Creating /Users/liam/work/releases/onap/policy/parent/releases/3.5.5.yaml
generating commit for policy/parent release: 3.5.4-->3.5.5 . . .
generating commit 'Release policy/parent: 3.5.5' . . .
[jakarta 2f0ceb1] Release policy/parent: 3.5.5
 1 file changed, 4 insertions(+)
 create mode 100644 releases/3.5.5.yaml
commit 'Release policy/parent: 3.5.5' generated
sending commit 'Release policy/parent: 3.5.5' to gerrit . . .
remote: 
remote: Processing changes: refs: 1, new: 1        
remote: Processing changes: refs: 1, new: 1, done            
remote: 
remote: SUCCESS        
remote: 
remote:   https://gerrit.nordix.org/c/onap/policy/parent/+/15333 Release policy/parent: 3.5.5 [NEW]        
remote: 
To ssh://gerrit.nordix.org:29418/onap/policy/parent
 * [new reference]   HEAD -> refs/for/jakarta
commit 'Release policy/parent: 3.5.5' sent to gerrit . . .
commit for policy/parent release: 3.5.4-->3.5.5 generated
Generated artifact release yaml file and commit for policy/parent

The onap/policy/parent/releases/3.5.5.yaml file is created and a commit is raised on gerrit.

The commit is reviewed and merged as normal.

Branching the Repositories

...