Group / Sub-group support for the GitLab NuGet Repository
You can use GitLab Packages for publishing and installing your NuGet dependencies. But you've been limited to using a project-level endpoint. For organizations with many projects or groups, this is quite inconvenient. You need to give your team a single URL for installing packages and don't want them to have to remember which package comes from where.
GitLab Packages now supports a group/sub-group endpoint for pulling all of your group's NuGet packages. The endpoint currently supports downloading and searching for NuGet packages.
Problem to solve
The NuGet repository only allows you to publish and install packages to/from a specific project. This can be problematic for complex organizations that have many different projects nested inside of a group/sub-group. These organizations need an easy way to pull dependencies from their group.
Help .NET/C# developers at larger organizations by introducing a group endpoint that will allow developers to install and search for packages amongst their entire group, not just a singular project.
- Follow what we do for Maven: at the group level, locate the possible packages and return the one with the highest
id. By avoiding the naming convention, we avoid more restrictions on the group level endpoint. Maven packages.
- Only pull actions (install and search) will be supported.
- Publishing packages will still be done with a project-level endpoint. Although they can be viewed in the group's package registry or using the Packages APIhttps://docs.gitlab.com/ee/api/packages.html#within-a-group.
User experience goal
- It's easy for teams to search for and install their group's NuGet dependencies### Documentation