CNB Docs

English

简体中文

English

简体中文
简体中文

Appearance

Generic Artifact Registry

Copy page

About 417 wordsAbout 1 min

Prerequisites

  1. Create Artifact Registry
  2. Get Artifact Registry Address
  3. Create Token

Push Artifacts

Credential Setup

Before pushing or pulling artifacts, configure .netrc authentication credentials (one-time setup):


printf "machine generic.cnbprod.alpha.qq.com\nlogin cnb\npassword %s\n" "${CNB_TOKEN}" > ~/.netrc

For how to obtain CNB_TOKEN, refer to Creating an Access Token.

Local Command Line Push

After configuring credentials, run the following command to push artifacts (replace <REPO_URL>, <PACKAGE>, <VERSION>, <LOCAL_FILE_NAME> with actual values):

curl --netrc '<REPO_URL>/<PACKAGE>?version=<VERSION>' -T '<LOCAL_FILE_NAME>'

Push in Cloud Native Build

  1. Add the following content to .cnb.yml and commit to your repository. Push a Tag to trigger the build; the Tag value will be used as the artifact version:
.cnb.yml
$:
  tag_push:
    - docker:
        image: curlimages/curl
      stages:
        - name: setup netrc
          script: printf "machine generic.cnbprod.alpha.qq.com\nlogin cnb\npassword %s\n" "${CNB_TOKEN}" > ~/.netrc
        - name: upload
          script: curl --netrc "<REPO_URL>/<PACKAGE>?version=${CNB_BRANCH}" -T "<LOCAL_FILE_NAME>"

Replace <REPO_URL>, <PACKAGE>, <LOCAL_FILE_NAME> with actual values. It is recommended to use Semantic Versioning.

Push in Workspaces

  1. Click the "Workspaces" button in the upper right corner of the repository page to enter the development environment
  2. After configuring credentials, run the push command (same as Local Command Line Push):
curl --netrc '<REPO_URL>/<PACKAGE>?version=<VERSION>' -T '<LOCAL_FILE_NAME>'

Use Artifacts

Pull Artifacts

If .netrc credentials are already configured (see tip in Push Artifacts section above), pull directly:

curl -OfL --netrc '<REPO_URL>/<PACKAGE>?version=<VERSION>'

(replace <REPO_URL>, <PACKAGE>, <VERSION> with actual values)

Delete Artifacts

Generic artifact registry does not support command-line deletion yet. Please refer to Delete Artifacts.

FAQ

Q1: Package Name Restriction Rules

Package name refers to the full path, for example a/b/c.txt.

  1. Maximum length is 128 characters, with a maximum depth of 5 levels
  2. Case-sensitive: a/b/c.txt and A/B/C.TXT are different paths
  3. Directory and file cannot share the same name: a/b/c and a/b/c/ cannot coexist
  4. Path segments cannot start or end with spaces
  5. A single - cannot be used as a directory or file name
  6. Package name characters must match the regex: ^[a-zA-Z0-9\u4e00-\u9fa5._\\-/ ]+$
© 2026 cnb.cool