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.
CodeArts Artifact
CodeArts Artifact
- 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?
On this page
Show all
Clearing Policies
Updated on 2023-11-28 GMT+08:00
A release repo automatically clear files on a scheduled basis. You can set a clearing policy to move expired files from the repository to the recycle bin or delete them permanently from the recycle bin based on the specified retention periods.
- Access the release repo by following instructions in Accessing Through a Specific Project.
- Click Settings at the upper right corner of the page. The Clearing Policies page is displayed.
- Enable Move expired files to the Recycle Bin or Clear from Recycle Bin as required, and select a retention period from the drop-down list.
Default retention periods:
- Move expired files to the Recycle Bin: 30 days
- Clear from Recycle Bin: 30 days
You can also customize a period. Click Customize, enter a number, and click √ to save.
NOTE:
Parameters below are optional.
- Skip Released files: The system retains files in the production package state when deleting files. For details, see Setting Status.
- Skip specified paths: When cleaning up files, the system retains the software package that matches the file path set by the user. You can set multiple file paths (starting with a slash (/) and separated by semicolons (;)).
Parent topic: Release Repo
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.