- What's New
- Function Overview
- Service Overview
-
Getting Started
- Uploading Software Packages to Release Repos
- Uploading Components to Maven Repository
- Releasing/Obtaining a Maven Component via a Build Task
- Releasing/Obtaining an npm Component via a Build Task
- Releasing/Obtaining a Go Component via a Build Task
- Releasing/Obtaining a PyPI Component via a Build Task
- Uploading/Obtaining an RPM Component Using Linux Commands
- Uploading/Obtaining a Debian Component Using Linux Commands
-
User Guide
- CodeArts Artifact User Guide
- Release Repos 2.0
- Self-Hosted Repos 2.0
- Release Repos 1.0
- Self-Hosted Repos 1.0
- Whitelist for All Accounts
-
Best Practices
- CodeArts Artifact Best Practices
- Releasing Maven Components and Archiving to a Self-Hosted Repo
- Releasing/Obtaining an npm Component via a Build Task
- Releasing/Obtaining a Go Component via a Build Task
- Releasing/Obtaining a PyPI Component via a Build Task
- Uploading/Obtaining an RPM Component Using Linux Commands
- Uploading/Obtaining a Debian Component Using Linux Commands
- Batch Migrating Maven/npm/PyPI Components to a Self-Hosted Repo
- API Reference
-
FAQs
- Release Repo
-
Self-Hosted Repo
- How Do I Upload Snapshots to a Maven Repository?
- How Do I Pull Components from a Maven Repository?
- Can I Call Software Packages in Self-Hosted Repos During Local Builds?
- What Should I Do With Error Code 500 When Uploading Maven Package for a Gradle Build?
- Why Did the Dependency WAR or JAR Files Fail to Be Downloaded?
- Why Is Error 401 Returned When Uploading Maven Components to Self-Hosted Repos?
- General Reference
Copied.
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 application scenarios.
Best Practice |
Description |
---|---|
Releasing Maven Components and Archiving to a Self-Hosted Repo |
CodeArts Artifact focuses on and manages the staging software 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 paths, code branch information, build tasks, creators, and build time. Throughout the development process, the software package is continuously refined across different versions. The management of software packages and their properties is the basis of release management. Therefore, developers need to regularly review the version history of software packages. This practice describes how to archive a Maven component by version to a self-hosted repo via a build task. |
A self-hosted repo manages private component packages (such as Maven) corresponding to various development languages. Different development language components vary in the archive format. A self-hosted repo manages private development language components and shares them with other developers in the same enterprise or team. This practice describes how to release a component to an npm repository via a build task and obtain a dependency from the repository for deployment. |
|
This practice describes how to release a component to a Go repository via a build task and obtain a dependency from the repository for deployment. |
|
This practice describes how to release a component to a PyPI repository via a build task and obtain a dependency from the repository for deployment. |
|
This practice describes how to use Linux commands to upload a component to an RPM repository and obtain a dependency from the repository. |
|
This practice describes how to use Linux commands to upload a component to a Debian repository and obtain a dependency from the repository. |
|
Batch Migrating Maven/npm/PyPI Components to a Self-Hosted Repo |
Self-hosted repos allow you to manually upload and download components. They can also interconnect with your local development environment to upload and download components. Uploading numerous packages one at a time can be cumbersome. You can use the migration tool provided by self-hosted repos to upload components in batches from Nexus or other repositories. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot