هذه الصفحة غير متوفرة حاليًا بلغتك المحلية. نحن نعمل جاهدين على إضافة المزيد من اللغات. شاكرين تفهمك ودعمك المستمر لنا.
- 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.
Managing Software Packages 1.0
Uploading Software Packages 1.0
- Access Release Repos 1.0.
- Click Upload.
- In the displayed dialog box, enter the required information and click Upload.
- Target Repository: current Release Repos.
- Version: set the version number for software packages.
- Upload Mode: select Single file or Multiple files. Single file is selected by default here.
- Path: After you set the path name, a folder with that name is created in the Repo View, where the uploaded software packages will be stored.
- File: select software packages from your local PC to upload.
- The uploaded software package is saved in the file list of Release Repos.
Click
in the Operation column of a software package to change its name.
Click
in the Operation column of a software package to download it to the local PC.
Click
in the Operation column of a software package to delete it.
Viewing/Editing Software Packages in Release Repos 1.0
On the Release Repos page, you can view or edit the software package details, including basic information, build information, and build packages.
Access the Release Repos homepage and click the name of a software package. A drawer is displayed, showing the software package details. The Release Repos details are displayed on the Basic Information, Build Information, and Build Packages tab pages.
- The Basic Information tab page displays the software package name, version, size, path, download address, creator, creation time, checksum, and other information.
You can click
in the upper right corner to change the name and release version of the software package. (The release version archived by CodeArts Build is the build sequence number by default.)
- The Build Information tab page displays the build task, build No., builder, code repository, code branch, and commit ID of the generated software package. Click Build Task to link to the task in CodeArts Build.
- The Build Packages tab page displays the archiving records of software packages uploaded through build tasks. You can click
to download a package.
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