[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29611#comment-29611 ] Martin Sivak commented on OVIRT-1299: ------------------------------------- The difference is that you depend on gerrit and on specific branch name to know which build-artifact script to execute. My requests does not require that, I will provide the git url and tarball url (or a dir with those) instead. Something very similar to what I want is the releng tools repository Sandro uses. An example: https://gerrit.ovirt.org/gitweb?p=releng-tools.git;a=blob;f=releases/ovirt-4... The only issue we have with this is that it is not properly documented (inheritance rules, ...), does not support source tarballs and CI is probably not using it at all.
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)