Versions Compared

Key

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

...

Beijing ONAP Signing Process

All ONAP leverages the LF signing process to sign all Nexus 2 Maven ONAP artifacts are signed using the following process.

  1. When a the PTL determines that an artifact is ready to sign, The PTL emails the LF helpdesk with the name of the Nexus 2 Maven artifact to be signed
  2. The LF helpdesk downloads the artifact from the staging repository, signs the artifact using the LF private key stored on a USB, and pushes the signed artifact to the release repository.

Nexus 3 Maven artifacts, Docker containers, are produced by ONAP, but there is currently no signing process for these artifacts. The LF is working on signing Nexus 3 Maven artifacts.

Casablanca ONAP Signing Process

Continue using the existing Beijing ONAP signing process to sing Nexus2 Maven Artifacts. Sign Casablanca Docker containers using the LF Nexus 3 Maven artifact signing process if it is available in time.

OpenDaylight (ODL) Signing Process

...