On Tue, Nov 16, 2021 at 9:43 PM Milan Zamazal <mzamazal@redhat.com> wrote:

Hi,

putting recently experienced problems with OST runs failures aside, I wonder about what currently happens in gerrit on gating. For instance in https://gerrit.ovirt.org/c/vdsm/+/117523/6:

- OST OST -1 Patch Set 6: OST-1 https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger1/4579 : Looking for build artifacts for OST. ci build

* Why setting OST-1 when looking for a build?

- Jenkins CI Patch Set 6:

No Builds Executed

https://jenkins.ovirt.org/job/vdsm_standard-check-patch/30672/ : To avoid overloading the infrastructure, a whitelist for running gerrit triggered jobs has been set in place, if you feel like you should be in it, please contact infra at ovirt dot org.

* OST not allowed to trigger builds?

- OST OST +1 Patch Set 6: OST+1

https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger1/4583 : start OST for https://jenkins.ovirt.org/job/vdsm_standard-check-patch/30681/

* Shouldn't OST set OST+1 after it runs rather than when it starts?

Is there any explanation of these phenomenons?

I have seen the same issues in the last week. I think we should start moving the project to github or gitlab instead of wasting time on fixing the legacy CI. This is a good time to do this. Nir