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
Configuring the Artifact Cleanup Strategy
You can automatically and manually delete artifacts that meet deletion conditions in batches. When a user creates a self-hosted Maven repo, the storage repositories include Release and Snapshot.
The snapshot of a Maven artifact is a special version that specifies a copy of the current development progress, and is different from a common version. Maven checks a new snapshot in the remote repository during each build and provides the maximum number of snapshot versions that can be retained and the function of automatically clearing expired snapshot versions.
The artifact cleanup strategy reduces the waste of storage space, makes artifacts in the repository clear, and ensures that artifacts are transferred in order during development, testing, deployment, and release.
Procedure
- Access the self-hosted repo by following instructions in Accessing Through a Specific Project.
- Select the corresponding Snapshot self-hosted Maven repo from the repository list on the left and click Settings in the upper right corner of the page.
- Click the Clearing Policies tab.
- Set the maximum number of Snapshot Count. The value ranges from 1 to 1000.
When the version of an artifact package exceeds this value, the package of the earliest version is overwritten by the package of the latest version.
- Enable automatic cleanup (No by default). Click Yes and enter the number of days. Snapshot versions that have been stored for more than the specified number of days will be automatically cleaned up.
The automatic cleanup time cannot be less than 1 day or greater than 100 days.
- Click Save to complete configuration.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.