[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories

[Martin Sivak (oVirt JIRA)]

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

Martin Sivak edited comment on OVIRT-1299 at 4/5/17 1:00 PM:
-------------------------------------------------------------

Do not make this more complex than it has to be. A simple text or ini file (in ovirt specific repository, not in the project itself!) where the maintainer can say which build (a link to jenkins, copr, koji, github, ...) should go to which release is enough. The same for source tarball. Just let us provide a link (git hash url, gitweb export or github for example).

All your tooling like publishers or CI or anything else can then consume this configuration without forcing us to use a fixed tag or branch structure. The maintainer should be in control of the releases or platform, not the automation.

oVirt is a distribution of pieces and some pieces have slightly different development model. Even some core oVirt project use GitHub as the primary source now.

This has been discussed couple of times already, for example here http://lists.ovirt.org/pipermail/devel/2017-February/029439.html and here http://lists.ovirt.org/pipermail/devel/2017-January/029161.html



was (Author: msivak at redhat.com):
Do not make this more complex than it has to be. A simple text or ini file where the maintainer can say which build (a link to jenkins, copr, koji, github, ...) should go to which release is enough. The same for source tarball. Just let us provide a link (git hash url, gitweb export or github for example).

All your tooling like publishers or CI or anything else can then consume this configuration without forcing us to use a fixed tag or branch structure. The maintainer should be in control of the releases or platform, not the automation.

oVirt is a distribution of pieces and some pieces have slightly different development model. Even some core oVirt project use GitHub as the primary source now.

This has been discussed couple of times already, for example here http://lists.ovirt.org/pipermail/devel/2017-February/029439.html and here http://lists.ovirt.org/pipermail/devel/2017-January/029161.html


> Please provide a koji (and if possible bodhi) instance for ovirt repositories
> -----------------------------------------------------------------------------
>
>                 Key: OVIRT-1299
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1299
>             Project: oVirt - virtualization made easy
>          Issue Type: New Feature
>          Components: Repositories Mgmt
>            Reporter: sbonazzo
>            Assignee: infra
>
> Some of the maintainers of oVirt project wants to have control on the builds going into the release repositories without 3rd party intervention on it.
> They would like to have a dist-git + koji like developer experience.
> A bodhi instance would help reviewing the package before it lands on repositories.



--
This message was sent by Atlassian JIRA
(v1000.883.0#100040)