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.
Before you begin:
- Prepare a Linux environment.
- Create an artifact repository (see Basic Operations).
- Select RPM as the repository type.
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:
Visit the RPM artifact website to search for an artifact and download and install it.
Click Generate configuration from access token in "Guide". A personal token will be generated as your access credential. You can manage your personal token in Personal Account Settings > Access Token.
After entering your login password, copy the configuration generated to the local
/etc/yum.repos.d/rpm-go.repo file. If this file does not exist, create one.
Run the rpm publish command to push an RPM package.
Run the command in the guide to pull an artifact.
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 CODING-AR does not automatically store RPM artifacts pulled from the proxy, check:
- Whether you have the permission to push artifacts to this repository.
- Whether the artifacts already exist in your local cache.