Tell me what is the difference between group endpoint and project endpoint in Gitlab's…
- User
Tell me what is the difference between group endpoint and project endpoint in Gitlab's nuget package registry? If i publish the nuget package in project, is it going to be available in group endpoint?
- Assistant
🔎 What’s the difference?
-
Project-scoped NuGet endpoint
• URL pattern:
https://<gitlab>/api/v4/projects/<project-id>/packages/nuget
• The package is stored inside that one project’s Package Registry.
• The feed only lists the packages that live in that project.
• Permissions are checked against the project (Guest+ to install, Maintainer+ to publish, or CI_JOB_TOKEN). -
Group-scoped NuGet endpoint
• URL pattern:
https://<gitlab>/api/v4/groups/<group-id>/-/packages/nuget
• Acts as a “virtual” feed for the whole group:
– Packages pushed directly to the group.
– ALL packages that exist in any project or subgroup underneath the group.
• One URL for consumers, so your dev machines or build agents don’t need to know which individual project produced the package.
• Permissions are checked against the group (Guest+ to install, Developer+ or a PAT with write_package to publish).
🛠️ Publishing rules
• Publish to a project →
– Package is physically stored in that project.
– Instantly becomes visible in:
a) that project’s endpoint, and
b) the parent group endpoint(s).
– Works fine withCI_JOB_TOKEN.• Publish to a group (supported in GitLab 13.8+) →
– Package is stored at the group level.
– Visible in the group feed and any parent group feeds.
– Not shown in individual project endpoints because it isn’t tied to a project.
– Requires a personal/group access token (write_packageorwrite_api).So, to your specific question:
“If I publish the NuGet package in a project, is it going to be available in the group endpoint?”
✅ Yes. The moment the push succeeds, the package is indexed by the group feed, and you (or anyone with access to the group) can install it using the group URL.🚀 Quick example
# Inside project CI job – publish to project feed dotnet nuget push bin/Debug/FooBar.1.0.0.nupkg \ --source "https://gitlab.com/api/v4/projects/${CI_PROJECT_ID}/packages/nuget" \ --api-key "${CI_JOB_TOKEN}" # On a developer workstation – consume through the group feed dotnet nuget add source \ --name GitLabGroup \ "https://gitlab.com/api/v4/groups/<group-id>/-/packages/nuget" \ --username <gitlab-username> \ --password <PAT-with-read_package>📌 Things to remember • Visibility cascades upward (project → group), never downward (group → project).
• CI_JOB_TOKEN only works for project endpoints (install and publish).
• For group push you need a PAT or Deploy Token scoped to the group.
• If the group or project is Private, consumers must authenticate; if the group is Public, unauthenticated installs are allowed by default.That’s the gist—happy packaging! 🎁
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.