The content of this page has been automatically translated by AI. If you encounter any problems while reading, you can view the corresponding content in Chinese.
This document describes how to store RPM artifacts in CODING-AR for centralized artifact management and version control. The following sections introduce how to create an artifact, configure authentication, and pull and push artifacts.
RPM is installed in Linux by default. You can run rpm commands in a Linux terminal directly. To use rpm commands in other operating systems, use Docker to install CentOS:
docker run -it --name centos centos:8 /bin/bash
Download a Demo Project
Go to the rpm artifact download page, search for the artifact package, download it to the local machine, and then install it.
Click on Operation Guide and the Generate Personal Token as Credential option will automatically generate and set the credential.
Copy the generated code to the local /etc/yum.repos.d/rpm-go.repo file. If the file does not exist, please create it.
Push an Artifact
Run the rpm publish command to push an RPM package.
curl -u [ username /email] -X POST [repository URL provided in the push guide] -T [artifact name].rpm
After the artifact is pushed successfully, refresh the page to view the latest artifacts.
Pull an Artifact
Run the commands provided in the page guide to complete the pull operation.
Configure a Proxy
RPM repositories have a default proxy address. You can configure other addresses.
Configure the remote proxy repository URL, pull artifacts in the repository to the local machine, and the artifacts will be automatically backed up to CODING-AR.
If the RPM Artifact Repository does not have a Storage Proxy RPM Artifact, there could be two reasons:
1. Whether you have the permission to push artifacts to this repository.
2. Whether the artifacts already exist in your local cache.
