[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29610#comment-29610 ] Barak Korren commented on OVIRT-1299: ------------------------------------- I'm not sure I understand the process, and how it differs from what we have now. A "build-artifacts" job can build in any way the developer chooses, including invoking remote build services. As long as it eventually leaves RPMs in exported-artifacts, they will be taken, system-tested and published. Every 'build-artifacts' job is also a package repository so you even get publishing "for free" without passing OST. If you want to separate the build/release process from source that is also easy to do, you just create a separate repo, place build scripts in it, and make them clone the "source" repo. This is essentially what the UX team did for various 3rd party dependencies. We will probably not further automate the use of specific build systems, nor is it probable that we will deploy any new build system. WRT GitHub - using it does not imply using a different process, we've been running a very oVirt-like process on GitHub for Lago for quite a long while now. And we've recently started doing this for other projects as well.

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)