User interface for the GitLab NuGet Repository
Problem to solve
The GitLab NuGet Repository allows developers to build, publish and share .NET packages, right alongside their source code and CI Pipelines. However, the MVC does not include a front end, which prevents users from viewing packages and package details from GitLab.
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
Add a front end to the NuGet Repository at the Project level to allow users to view, install and delete their packages, as well as download files.
This data will populate
Package Info (expanded)
This data will populate the top portion of
|P1||Last updated date|
We will utilize the UI pattern from our Conan implementation to include additional meta data section for NuGet packages. The below info will be included in an expandable table titled
|P2||Require License Acceptance|
In the user interface we will allow developers to download the
.nupkg file associated with a given package.
.nupkg is a single zip file that contains:
- Compiled code (DLLs)
- Other files related to that code
- A descriptive manifest that includes information like the package's version number.
NOTE: NUPKG files are built from .NUSPEC files, which themselves are built from .DLL assemblies.
The NuGet Manifest
- Describes the package's contents and is itself included in the package.
- Drives both the creation of the package and instructs NuGet on how to install the package into a project. For example, the manifest identifies other package dependencies such that NuGet can also install those dependencies when the main package is installed.
Permissions and Security
Project Permissions: UI
|Pull from Maven, NPM, Conan, NuGet||x||x||x||x|
|Publish to Maven, NPM, Conan, NuGet||x||x||x|