Esta página aún no está disponible en su idioma local. Estamos trabajando arduamente para agregar más versiones de idiomas. Gracias por tu apoyo.
- Service Overview
-
Getting Started
- Getting Started with a Release Repo
- Getting Started with a Self-hosted Repo
- 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
-
FAQs
- Release Repo
-
Self-Hosted Repo
- How Do I Upload Snapshots to the Self-hosted Maven Repo?
- How Do I Call a Private Component from a Self-hosted Maven Repo?
- Can I Call Software Packages in Self-hosted Repos During Local Builds?
- Why Is Error Code 500 Returned When a Gradle Build Task Uploads a Maven Package?
- Why Can't the Repository Receive Requests?
- 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?
Show all
Constraints
Table 1 describes the constraints on CodeArts Artifact.
Category |
Item |
Limit |
---|---|---|
Browser |
Type |
The following browsers are supported:
Chrome and Firefox are recommended. |
Resolution |
Resolution |
(Recommended) 1280 x 1024 or higher |
Total storage capacity |
Release Repos and self-hosted repos |
Total capacity: 10 GB |
Total download capacity |
Traffic of Release Repos and self-hosted repos |
Total traffic: 5 GB/month |
Constraints on Release Repos |
Maximum size of a file uploaded on the console |
2 GB |
Maximum size of a file uploaded by a build task |
10 GB |
|
Constraints on self-hosted repos |
Maximum size of a file uploaded on the console |
Maven/npm/PyPI/Go/RPM/Debian/Conan: 100 MB NuGet: 20 MB |
Repository quantity |
|
|
Maximum size of a file uploaded by a build task |
2 GB |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.