We want to migrate away from Archiva and replace it with Gitlab as a Maven package registry. See parent task (T367315) and doc for more details.
We expect to host ~50G of packages over the next 5 years. We will not migrate the historical releases from Archiva to Gitlab.
My understanding is that we can create a global package registry in Gitlab, but if that's not the case, we could create one that is part of the ci-tools group or maybe a dedicated group. We do NOT want to have a registry per repo, and we would like to avoid having multiple registries linked to multiple groups. Having a single registry allow us to have that configuration centralized and transparent to all projects that need to use those dependencies.
Eventually, we want CI to upload artifacts to the registry, so most users should not need write access. During the implementation phase, to allow for experimentation, we want a few users to be able to upload packages manually for testing.
The registry should be readable anonymously by anyone.
AC:
- Gitlab package registry is created
- Registry is writable by members of the DPE SRE team
- Registry is publicly readable