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.
...
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.
Migration to DockerHub
There are few things to consider for this migration. Currently they are not well planned on regards on how should they be addressed but this is hopefully getting clearer as we go
- 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?