[ovirt-devel] Re: Integrating OST with artifacts built in github

> On 2. 12. 2021, at 19:09, Nir Soffer wrote: > > Looking this very helpful document > https://ovirt.org/develop/developer-guide/migrating_to_github.html > > The suggested solution is to create artifacts.zip with all the rpms > for a project. > > But to use the rpms in OST, we need to create

[ovirt-devel] Integrating OST with artifacts built in github

Looking this very helpful document https://ovirt.org/develop/developer-guide/migrating_to_github.html The suggested solution is to create artifacts.zip with all the rpms for a project. But to use the rpms in OST, we need to create a yum repository before uploading the artifacts, so we can pass a

[ovirt-devel] Re: Another CI failure

Fixed > On 1 Dec 2021, at 11:07, Milan Zamazal wrote: > > Ehud Yonasi writes: > >> It was a problem with global setup with el9 node - there was a missing >> package and it was removed in: >> https://gerrit.ovirt.org/c/jenkins/+/117867 >> > >

[ovirt-devel] Re: Updates on oVirt Node and oVirt appliance building outside Jenkins

> On 2. 12. 2021, at 13:19, Sandro Bonazzola wrote: > > Hi, just a quick update on current issues in trying to build oVirt Node and > the engine appliance outside Jenkins. > > 1) Using GitHub Actions: an attempt to build it is in progress here: >

[ovirt-devel] Re: oVirt Community - open discussion around repositories and workflows

> On 2. 12. 2021, at 12:51, Milan Zamazal wrote: > > Michal Skrivanek writes: > >>> On 1. 12. 2021, at 16:57, Nir Soffer wrote: >>> >>> On Wed, Dec 1, 2021 at 11:38 AM Milan Zamazal wrote: Michal Skrivanek writes: > Hi all, > so far we haven't encounter any

[ovirt-devel] Updates on oVirt Node and oVirt appliance building outside Jenkins

Hi, just a quick update on current issues in trying to build oVirt Node and the engine appliance outside Jenkins. 1) Using GitHub Actions: an attempt to build it is in progress here: https://github.com/sandrobonazzola/ovirt-appliance/pull/1 it's currently failing due to lorax not being able to

[ovirt-devel] Re: oVirt Community - open discussion around repositories and workflows

Michal Skrivanek writes: >> On 1. 12. 2021, at 16:57, Nir Soffer wrote: >> >> On Wed, Dec 1, 2021 at 11:38 AM Milan Zamazal wrote: >>> >>> Michal Skrivanek writes: >>> Hi all, so far we haven't encounter any blocking issue with this effort, I wanted to propose to decide on

[ovirt-devel] Re: oVirt Community - open discussion around repositories and workflows

> On 1. 12. 2021, at 16:57, Nir Soffer wrote: > > On Wed, Dec 1, 2021 at 11:38 AM Milan Zamazal wrote: >> >> Michal Skrivanek writes: >> >>> Hi all, >>> so far we haven't encounter any blocking issue with this effort, I >>> wanted to propose to decide on oVirt development moving to GitHub,

[ovirt-devel] Re: COPR's ovirt-master-snapshot replacing resources.ovirt.org's "tested" repo

> On 2. 12. 2021, at 12:07, Michal Skrivanek > wrote: > > Hi all, > COPR[1] is effectively replacing the "tested" repo - the one that gets all > built artifacts after a patch is merged (and is actually not tested:) > > Sandro started to move projects to COPR for merged patches some time ago

[ovirt-devel] COPR's ovirt-master-snapshot replacing resources.ovirt.org's "tested" repo

Hi all, COPR[1] is effectively replacing the "tested" repo - the one that gets all built artifacts after a patch is merged (and is actually not tested:) Sandro started to move projects to COPR for merged patches some time ago and we believe it's complete except appliance and node. So we can all