[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren reassigned OVIRT-1299: --- Assignee: Barak Korren (was: infra) > 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: Barak Korren > > 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.910.0#100040) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=29615#comment-29615 ] Michal Skrivanek commented on OVIRT-1299: - +1 for ovirt-web-ui, we're going to use the same flow > 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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=29614#comment-29614 ] Martin Sivak commented on OVIRT-1299: - Exactly what I would like to achieve. With one improvement in step 3. I usually release in the same copr repo so in the ideal world I would just provide the repo url once and every time you do a compose (or nightly) the tooling would check for updates. > 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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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.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. > 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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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: msi...@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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=29607#comment-29607 ] Martin Sivak commented on OVIRT-1299: - 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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sbonazzo updated OVIRT-1299: Epic Link: OVIRT-411 > 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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
sbonazzo created OVIRT-1299: --- Summary: 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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
