CNB Docs

English

简体中文

English

简体中文
简体中文

Appearance

Nuget Artifact Registry

Copy page

About 1264 wordsAbout 4 min

Prerequisites

  1. Create Artifact Registry
  2. Obtain Artifact Registry Address
  3. Create Access Token

Local Usage

Client Instructions

Client/Tooldotnet CLInuget.exe
Use Case.NET Core/.NET 5+ projectsLegacy .NET Framework projects
Cross-platform SupportNative supportRequires Mono
InstallationInstalled with .NET SDK, no additional setupRequires downloading nuget.exe

Credential Management Commands

Use CNB's access token as login credentials. Configuration commands:

dotnet CLI

Replace <YOUR_TOKEN> with the access token, <SOURCE_NAME> with a custom source name, <REPO_URL> with the Artifact Registry address:

dotnet nuget add source <REPO_URL> --name <SOURCE_NAME> --username cnb --password <YOUR_TOKEN> --store-password-in-clear-text
# Example: Add credential cnb-nuget-repo
# dotnet nuget add source https://nuget.cnb.cool/cnb/nuget-repo/-/packages/v3/index.json --name cnb-nuget-repo --username cnb --password <YOUR_TOKEN> --store-password-in-clear-text

dotnet nuget list source

Replace <SOURCE_NAME> with a custom source name:

dotnet nuget remove source <SOURCE_NAME>
# Example: Remove credential for cnb-nuget-repo source
# dotnet nuget remove source cnb-nuget-repo

Client/Tool
Windows%AppData%\NuGet\NuGet.Config
Linux/macOS~/.config/NuGet/NuGet.Config or ~/.nuget/NuGet/NuGet.Config

Artifact Management Commands

Configure credentials before executing artifact management commands.

dotnet CLI

Replace <PACKAGE_NAME> with the package name, <VERSION> with the version number, <SOURCE_NAME> with a custom source name:

dotnet add package <PACKAGE_NAME> --version <VERSION> --source <SOURCE_NAME>
# Example: Pull version 1.0.0 of mynupkg package from the Artifact Registry named cnb-nuget-repo
# dotnet add package test --version 1.0.0 --source cnb-nuget-repo

Replace <CSPROJ_PATH> with the .csproj file path, <PKG_PATH> with the nupkg package output path, <VERSION> with the version number:

dotnet pack <CSPROJ_PATH> -p:PackageVersion=<VERSION>  --configuration Release --output <PKG_PATH>
# Example: Build artifact
# dotnet pack mynupkg.csproj --configuration Release --output nupkgs
# Or build a specific version artifact
# dotnet pack mynupkg.csproj -p:PackageVersion=1.0.0 --configuration Release --output nupkgs

Replace <NUPKG_PATH> with the nupkg package path, <SOURCE_NAME> with a custom source name, <YOUR_TOKEN> with the access token:

dotnet nuget push <NUPKG_PATH> --source <SOURCE_NAME> -k <YOUR_TOKEN>
# Example: Push version 1.0.0 of mynupkg package
# dotnet nuget push ./mynupkg.1.0.0.nupkg --source cnb-nuget-repo -k <YOUR_TOKEN>

Replace <PACKAGE_NAME> with the package name, <VERSION> with the version number, <SOURCE_NAME> with a custom source name:

dotnet nuget delete <PACKAGE_NAME> <VERSION> --source <SOURCE_NAME>
# Example: Delete version 1.0.0 of mynupkg package from cnb-nuget-repo source
# dotnet nuget delete mynupkg 1.0.0 --source cnb-nuget-repo

Replace <PACKAGE_NAME> with the package name, <SOURCE_NAME> with a custom source name:

dotnet package search <PACKAGE_NAME> --source <SOURCE_NAME>
# Example: Query packages containing mynuget from the Artifact Registry named cnb-nuget-repo
# dotnet package search mynuget --source cnb-nuget-repo

dotnet nuget locals http-cache --clear

dotnet nuget locals all --clear

Usage in Cloud Native Build and Workspaces

The following example covers both CI auto-build and Workspace development scenarios, sharing the same package management commands:

.cnb.yml
# CI: auto-build and push nupkg on push
main:
  push:
    - docker:
        image: mcr.microsoft.com/dotnet/sdk:9.0
      stages:
        - name: add nuget source
          script: dotnet nuget add source https://nuget.cnb.cool/cnb/nuget-repo/-/packages/v3/index.json --name cnb-nuget-repo --username ${CNB_TOKEN_USER_NAME} --password ${CNB_TOKEN} --store-password-in-clear-text
        - name: pack
          script: dotnet pack mynupkg.csproj --configuration Release --output nupkgs
        - name: push
          script: dotnet nuget push nupkgs/*.nupkg --source cnb-nuget-repo -k ${CNB_TOKEN}

# Dev: configure dotnet dev environment, then run the three commands below manually
$:
  vscode:
    - docker:
        image: mcr.microsoft.com/dotnet/sdk:9.0

In a Workspace, enter the terminal and manually run:

dotnet nuget add source https://nuget.cnb.cool/cnb/nuget-repo/-/packages/v3/index.json --name cnb-nuget-repo --username cnb --password ${CNB_TOKEN} --store-password-in-clear-text
dotnet pack mynupkg.csproj --configuration Release --output nupkgs
dotnet nuget push "nupkgs/*.nupkg" --source cnb-nuget-repo -k ${CNB_TOKEN}

FAQ

Q1: Encountered 401 Forbidden error

Possible cause: Insufficient permissions for the credential.

Solution: Reconfigure the access token with the required permissions. Token acquisition: Personal Settings -> Access Tokens -> Add Access Token -> Select the appropriate permissions for the Artifact Registry.

Q2: Encountered 403 Forbidden error

Possible cause: Incorrect credential configuration.

Solution: Configure the correct access token for the Artifact Registry. Token acquisition: Personal Settings -> Access Tokens -> Add Access Token -> Select the appropriate permissions for the Artifact Registry.

Q3: Encountered 409 Forbidden error

Possible cause: Package already exists and overwriting is not allowed.

Solution: To overwrite the package, go to the corresponding Artifact Registry -> Artifact Registry Settings -> Policy Management -> Select "Allow Overwriting Existing Versions".

Q4: How to support HTTP

Possible cause: Client only supports HTTPS by default.

Solution:

Client/ToolHTTP support
dotnet CLISpecify --allow-insecure-connections when adding the repository credential
nuget.exeSpecify -AllowInsecureConnections when adding the repository credential

More Usage

For more NuGet usage, please refer to the NuGet official documentation.

© 2026 cnb.cool