Hi All,
I've been working on adding GitHub Actions-based CI to vdsm today.
Feel free to check out the patches here:
https://gerrit.ovirt.org/q/topic:%22github-actions-ci%22+(status:open%20OR%20status:merged)
Some comments:
- the linters work fine already, we can start using them
- RPM
Hi,
In ovirt-engine pom.xml there's a requirement for build time
on ovirt-engine-extensions-api = 1.0.0.
This dependency is available on maven central so online build works.
Any clue on why we are not requiring 1.0.1
Sorry, but I don't see any improvements since morning, all engine
check-patch jobs are still failing:
17:50:07 Initialized empty Git repository in
/home/jenkins/agent/workspace/ovirt-engine_standard-check-patch/ovirt-engine/.git/
17:50:51
Hi Nir,
There was a problem in jenkins to switch to the new k8s stack on IBM cloud, a
restart was required and now it’s solved.
> On 25 Nov 2021, at 21:53, Nir Soffer wrote:
>
> On Thu, Nov 25, 2021 at 9:15 PM Michal Skrivanek
> mailto:michal.skriva...@redhat.com>> wrote:
>>
>>
>>
>> On
On Fri, Nov 26, 2021 at 10:34 AM Sandro Bonazzola
wrote:
>
>
> Il giorno gio 25 nov 2021 alle ore 20:46 Ehud Yonasi
> ha scritto:
>
>> Indeed Martin, I can see it now.
>> We have an issue reflecting the new resources server, probably dns or
>> something related.
>>
>> Meanwhile Shani, I suggest
Il giorno lun 15 nov 2021 alle ore 11:55 Sandro Bonazzola <
sbona...@redhat.com> ha scritto:
>
>
> Il giorno lun 15 nov 2021 alle ore 10:22 Artur Socha
> ha scritto:
>
>> Ack.
>> @Sandro, please let me know if ~EOY timeline is good enough.
>>
>
> Should be good enough
>
I rebuilt the needed
Il giorno gio 25 nov 2021 alle ore 20:46 Ehud Yonasi
ha scritto:
> Indeed Martin, I can see it now.
> We have an issue reflecting the new resources server, probably dns or
> something related.
>
> Meanwhile Shani, I suggest that you change the resources server in your
> automation/*.repos file
