Hi Didi,

You recall correctly.

Right now the process of getting rpms publishing to nightly is as follows:

1) Merge the patch in the project

2) It will end up in CQ, and if the build-artifacts job (check-merged) finishes successfully, it will be published to tested.

3) There is a nightly run job called ovirt_${RELEASE}_publish-rpms_nightly that copy tested ${RELEASE} rpms into it.

If the rpm is not in nightly that might be because the check merged job failed (which it didn't because you clearly see it in tested), then it probably happened after the nightly job ran, and it will appear tomorrow.

If it's urgent, I can rerun the job. Please let me know.

Regards,

Ehud.

On Thu, Jul 16, 2020 at 12:57 PM Yedidyah Bar David <didi@redhat.com> wrote:

Hi all,

1. Yesterday mperina pushed and merged a patch [1] to hopefully solve
a rather-long-time breakage of, among others, he-basic-suite. I still
do not see it in master-snapshot [2] - only 19.1.0-1. I do see it in
tested [3]. Can someone please publish it to snapshot?

2. I tried to debug this myself a bit, but failed to find
documentation for the publishing part. A few months ago it was said
(not very clearly/officially, IIRC) that we do not anymore pass
built-artifacts results through OST, because it's too fragile. Did we
update docs? Where can I find a clear overview of the process from
pressing Merge to having an rpm in master snapshot?

Thanks and best regards,

[1] https://gerrit.ovirt.org/110324
[2] https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el8/
[3] https://resources.ovirt.org/repos/ovirt/tested/master/rpm/el8/
--
Didi
_______________________________________________
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/Q7QAW24L5AYRJVBFYWCTE7UW4DSFTSFN/