-
Notifications
You must be signed in to change notification settings - Fork 160
Labels
plugin | artifactRelated to the `prepare/artifact` plugin.Related to the `prepare/artifact` plugin.status | discussNeeds more discussion before closingNeeds more discussion before closing
Description
When adding a repository in the prepare step using a potential or proposed "repository-url" provider (which fetches and enables a remote .repo file), automatically set the repository priority to 1.
This ensures that packages from the artifact/testing repository take precedence over base system repositories, which is crucial for testing built RPMS/artifacts (e.g., in CI with scratch builds or custom repos).
Acceptance Criteria
- When the prepare plugin adds a repository from a remote URL (repository-url provider), the generated/enabled .repo file includes
priority=1. - Packages from this repository are preferred during installation (verified by installing a package available in both the artifact repo and base repos).
- No manual priority configuration is required for this use case.
This would provide consistency with other artifact-related preparation methods (e.g., COPR builds often need high priority).
coderabbitai
Metadata
Metadata
Assignees
Labels
plugin | artifactRelated to the `prepare/artifact` plugin.Related to the `prepare/artifact` plugin.status | discussNeeds more discussion before closingNeeds more discussion before closing