In addition to the basic settings and advanced settings that are common for all local repositories, the following settings are available when configuring RPM repositories.
Field | Description |
|---|---|
Primary Key Name | The name of the GPG primary key used by the repository. |
Secondary Key Name | The name of the GPG secondary key used by the repository. |
RPM Metadata Folder Depth | Informs Artifactory under which level of directory to search for RPMs and save the By default this value is 0 and refers to the repository's root folder. In this case, Artifactory searches the entire repository for RPMs and saves the Using a different depth is useful in cases where generating metadata for a repository separates its artifacts by name, version and architecture. This will allow you to create multiple RPM repositories under the same Artifactory RPM repository. For example: If the repository layout is similar to that shown below and you want to generate RPM metadata for every artifact divided by name, set the REPO_ROOT/$ARTIFACT_NAME/$ARTIFACT_VERSION/$ARCHITECTURE/FILE_NAME - or - rpm-local/foo/1.0/x64/foo-1.0-x64.rpmm NoteWhen changing the configured depth of existing repository, packages indexed in the old depth might need to be re-indexed or moved to a new depth to be available in the new configured depth, and YUM clients might need to change their configuration to point to the new depth.depth. |
Auto Calculate RPM Metadata | When set, RPM metadata calculation is automatically triggered by the actions described by the setting above. |
Enable File List Indexing | When set, RPM metadata calculation will also include indexing the |
RPM Group File Names | A comma-separated list of YUM group files associated with your RPM packages. Note that at each level (depth), the |