[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.p... ] eedri updated OVIRT-1441: ------------------------- Resolution: Won't Do Status: Done (was: To Do) As stated in the last comments, we shouldn't allow any new packages to be deployed to static repos. on the contrary, we have a ticket already to have them cleaned as they created multiple issues in the past and caused OST and other jobs to fail. the supported flows are mentioned in this ticket, it should either be external repo or internal oVirt package, which has a build-artifacts jobs. if there is a need to use a package that doesn't comply to any of the above, please open a ticket and explain the need and why it can't be done in the supported flows.
[RFE] Add a jenkins job for copying external packages to static repos ---------------------------------------------------------------------
Key: OVIRT-1441 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra
Description of problem: Currently, when we want to copy a package from elsewhere to resources.ovirt.org, we manually run repoman. It will be nice to have a jenkins job for this - with inputs probably being URLs of source packages/repos and target versions to copy to: 1. It will not require us anymore to login there and do sensitive stuff on it directly 2. It will have proper logs, allowing much more easily understand when a package was added, by whom, and even perhaps why. So better add to the inputs also 'Notes'. This is cloned from: https://bugzilla.redhat.com/show_bug.cgi?id=1455316 Best, -- Didi
-- This message was sent by Atlassian JIRA (v1000.1089.0#100053)