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

[Barak Korren (oVirt JIRA)]

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

Barak Korren commented on OVIRT-1299:
-------------------------------------

{quote}
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.
{quote}

It does not have to be in Gerrit, nor is there a need for specific branches ATM. The discussion about branches was trying to come up with a scheme to auto-detect things that are currently specified in the project YAML in the Jenkins repo. Since we did not implement that yet, you can use any branch names you'd like and map them to oVirt releases in the YAML file.

The one thing we do strongly depend on, is that every change starts with a commit somewhere so that we can track it, and use the hash as a reliable unique identifier for the change. I think this is important. Without it you cannot track changes.

{quote}
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.1.1.conf;h=f20c23f5f7d88225e2e729ebab552e5d69544c41;hb=0988bf1bd9d5f91f35733031571f1e8407e28647

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.
{quote}

That is a repoman configuration file. All it does is collect files together. This is not a reliable source of information, not is it located in the right place, because AFAIK deciding which package builds go to which oVirt releases is the responsibility of the individual package maintainers, not the integration team.

But still, I'm not sure I understand where you are trying to go. Let me try to describe the process you are tying to get to as I understand it:
# You merge a new commit to mom
# You go and launch a build in copr manually.
# When the build is done you go to some file in some repo, specify the url to the build in it and submit a new commit.
# Once the new commit is merged the CY system downloads the new build and publishes it in the oVirt repos.


> 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)