[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos

Yedidyah Bar David (oVirt JIRA) jira at ovirt-jira.atlassian.net
Wed Jun 14 13:15:43 UTC 2017


    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32209#comment-32209 ] 

Yedidyah Bar David commented on OVIRT-1441:
-------------------------------------------

On Wed, Jun 14, 2017 at 3:33 PM, Barak Korren (oVirt JIRA)

That's a good question from oVirt-metrics' perspective.
I am not sure.
For now we wanted something quick and this was the solution - build in
copr, copy to -static.

I am not saying it's the best solution. I did open the other ticket...

I am just suggesting it as a real-life use-case that we should consider when
designing how to compose our repos etc.





-- 
Didi


> [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.1045.3#100046)


More information about the Infra mailing list