Content Comparison

 Tracker and general tips: global-jjb Migration Tracker

...

 1, jjb must be updated with gerrit-maven-stage:
jobs:
  - gerrit-maven-stage:
      sign-artifacts: true
      build-node: centos7-builder-4c-4g
      maven-versions-plugin: true

  2, Oparent version must be updated to 2.0.0 , Otherwise "sign-artifacts" will fail and jjb log complains something like:

11:07:39 ---> sigul-sign-dir.sh
11:07:40 Signing Directory with Sigul...
11:07:40 find: ‘/w/workspace/multicloud-openstack-vmware-maven-stage-master/m2repo’: No such file or directory
11:07:40 ERROR: No files to sign. Quitting...

  3,pom.xml of a pom submodule must refer to root pom as parent , refers to oparent must be accompanied by version.properties in the same dir. Or it could refer to a parent which meet that requirement. e. g.

multicloud/openstack/version.properties

...

<parent>
    <groupId>org.onap.oparent</groupId>
    <artifactId>oparent</artifactId>
    <version>2.0.0</version>
    <!--relativePath>../oparent</relativePath-->
</parent>

<modelVersion>4.0.0</modelVersion>
<groupId>org.onap.multicloud.openstack</groupId>
<artifactId>multicloud-openstack-root</artifactId>
<version>1.4.0-SNAPSHOT</version>
<name>multicloud-openstack</name>

...

14:04:07 Uploaded in 0:00:01 seconds.
14:04:08 Completed uploading files to autorelease-148670.

*** Refering to oparent from submodule pom.xml Failed to meet that requirement will result in failing to rename the pom artifact version (e.g. rename it from 1.4.0-SNAPSHOT to 1.4.0),

...