In opnfv we have a method for projects to choose which ref they want to tag or branch on. Bringing this in to global-jjb.

This work was spurred from RT stats showing a high volume of ONAP tickets.

In order to reduce Jessica's workload, projects will be able to drive their own branching and tagging by modifying a release yaml file in the ci-management repo, RE's then just need to review and merge.

As a second step, in the realm of releasing artifacts for onap, and perhaps ODL.
I will extend this method to include fields for releasing artifacts in nexus.

something like:

ci-mangement/releases/branch/project.yaml

artifact:

• type: maven
  staging_location: 'https://nexus.onap.org/content/repositories/autorelease-100344/org/onap/aaf/authz/'
  version: 1.0.0

With a verify job that tests:
is it signed?
did the surce job pass?
does the directory exist and is it not empty?
is the destination empty

and a merge job that calls lftools nexus release.