You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

LF is working on optimizing the release process overall.

Our goal is to help PTLs and teams handle their releases as much as possible with little to no LF intervention.


Ongoing work for Nexus 2 Maven releases

For Nexus2 Maven releases, LF team is working on migrating the teams to use global-jjb {project-name}-maven-stage-{stream} 

This job performs the following:

  1. Removes "-SNAPSHOT" from all pom files so that the push can be done in staging
  2. Produces a taglist.log, project.patch, and project.bundle files
  3. Runs a mvn clean deploy to a local staging repo
  4. Pushes the staging repo to a Nexus staging repo https://nexus.onap.org/content/repositories/<REPO_ID> (REPO_ID is saved to staging-repo.txt on the log server)
  5. Archives taglist.log, project.patch, and project.bundle files to log server

Currently, having teams using {project-name}-maven-stage-{stream}  will already reduce the time LF takes to make a release to just the time it takes to make 1 click in Nexus2.

LF team is also working on automating that last step. 


Ongoing work for Nexus 3 Docker releases

Currently, there is no job in global-jjb that helps on this. 

Internally, we had some blockers while trying to add the signatures but now that this is possible in Maven artifacts we can start working on 

incorporating the same into Docker releases. 



  • No labels