CodeArts Artifact
CodeArts Artifact
- 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
On this page
Show all
Copied.
Clearing Policies 2.0
If files in Release Repos become redundant or invalid, you can use the scheduled auto-clearing policy to either move expired files to the recycle bin or delete outdated files from it. This helps you manage your Release Repos more efficiently and in an organized manner.
Setting Clearing Policies
- Click a project card to access the project, and choose Artifact > Release Repos from the menu bar.
- Click Settings in the upper right corner of the page and select Clearing Policies.
- 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 Recycle Bin: 30 days
- Clear from Recycle Bin: 30 days
Figure 1 Setting clearing policies- You can also set a period. Click Customize, enter a number, and click √ to save the setting.
NOTE:
Parameters below are optional.
- Skip released files: The system retains files in the production package state when clearing files. For details, see Setting Production Package Status.
- Skip specified paths: The system retains software packages that match the file paths set by users when clearing files.
- You can set multiple file paths, each starting with a slash (/) and separated by semicolons (;) but file path names cannot contain the project name. Example: /test/folder1/;/1.0.0/test.txt
- Spaces before and after the file path name will be automatically removed.
- The file path uses prefix matching. Ignore directories ending with a slash (/) and ignore files with a full file path. Otherwise, the ignored file may not match.
Parent topic: Release Repos 2.0
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot