Help Center/ CodeArts Artifact/ Best Practices/ CodeArts Artifact Best Practices
Updated on 2025-08-22 GMT+08:00

CodeArts Artifact Best Practices

This document summarizes the operation practices of CodeArts Artifact in common application scenarios. It provides detailed solutions for each practice, helping users easily use CodeArts Artifact in different scenarios.

Table 1 CodeArts Artifact best practices

Best Practice

Description

Releasing a Maven Artifact to a Self-Hosted Repo via a Build Task

CodeArts Artifact focuses on and manages the staging packages (usually built by or packed from the source code) and their lifecycle metadata. The metadata includes basic properties such as the name and size, repository URLs, code branch information, build tasks, creators, and build time. Throughout the development process, packages are continuously refined across different versions.

The management of packages and their properties is the basis of release management. Therefore, developers need to regularly review the version history of packages. This practice describes how to archive a Maven artifact by version to a self-hosted repo via a build task.

Releasing/Obtaining an npm Package via a Build Task

A self-hosted repo manages private packages (such as Maven) corresponding to various development languages. Different development languages use different package formats. A self-hosted repo manages private packages and shares them with other developers in the same enterprise or team.

This practice describes how to release a private package to an npm registry via a build task and obtain a dependency from the registry for deployment.

Releasing/Obtaining a Go Package via a Build Task

This practice describes how to release a private package to a Go repository via a build task and obtain a dependency from the repository for deployment.

Releasing/Obtaining a PyPI Package via a Build Task

This practice describes how to release a private package to a PyPI repository via a build task and obtain a dependency from the repository for deployment.

Uploading/Obtaining an RPM Package Using Linux Commands

This practice describes how to use Linux commands to upload a private package to an RPM repository and obtain a dependency from the repository.

Uploading/Obtaining a Debian Package Using Linux Commands

This practice describes how to use Linux commands to upload a private package to a Debian repository and obtain a dependency from the repository.

Migrating Maven/npm/PyPI Repositories from Nexus to Self-Hosted Repos

Self-hosted repos allow you to manually upload and download private packages. They can also interconnect with your local development environment to upload and download private packages. Uploading numerous packages one at a time can be cumbersome. You can use the migration tool provided by self-hosted repos to upload packages in batches from Nexus or other repositories.

Migrating Local Repository Data to CodeArts Artifact

CodeArts Artifact provides a batch migration tool to quickly migrate Maven repository and npm registry on local disks to the Maven repository and npm registry in self-hosted repos. This streamlines operations and maintenance for greater efficiency.

Configuring CodeArts Artifact Permissions

This practice uses self-hosted repos as an example to describe how to quickly manage permissions for individual repositories and by project.