LF is working on optimizing the release process overall.
...
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:
...
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.
...
- Tech teams make Nexus3 registry references in the code (pom.xml, Docker files...) We need to know how are the teams going to change these references to Dockerhub without disrupting much of their current procedures
- LF has to update the docker templates we have to publish to Dockerhub. We need to make sure we wither create a new template or make this information into a parameter we can slowly modify as we transition
- Currently DockerHub has all releases up to date, is the team going to need any snapshots?
Proposed migration plan and stakeholders
Activities happening or that can happen right now:
- Docker templates:
- RELENG: Templates for Maven-Docker projects → COMPLETED
- RELENG: Templates for Docker only projects → COMPLETED
- ONAP: Define component dependency chart → PENDING (1 hr, maybe a PTL meeting task June 17?) By examining jenkins jobs logs We could make preliminary list here https://paste.ubuntu.com/p/QwYKgSmg7P/
Order of activities that will happen after TSC approval and after Nexus2 migration (starting July 22):
- RELENG + ONAP + MULTIARCH: Schedule a call to plan the migration → 1 hr
- ONAP + MULTIARCH: Modify any docker registries mentions in the code and any changes to the code to make it multi-ach friendly. → (2 hr mini avarage, Time depends on # of components per project)
- ONAP + RELENG: Add global-jjb jobs in project yaml files. → 20 mins
- ONAP + RELENG + MULTIARCH: Test jobs and address any issues → Best case scenario 2 hr
- Verify that the right artifacts were produced and pushed into DockerHub -> 1 hr
- Attempt to run multi-architecture pulls and make sure DockerHub calls the right manifest -> 1 hr
- Functional tests? Scope and ETA need to be defined by tech team.
- ONAP: Confirm dependencies and needed images appear in Docker Hub. → 20 min
- ONAP + RELENG: Remove deprecated Nexus3 jobs → 20 min
Notice these are best case scenario situations. If any ONAP component requires an upgrade on the global-jjb jobs, such upgrade will need to be evaluated and developed by RELENG.
...