Hi, the `ovirt-engine-wildfly-19.1.0-2.el8.x86_64.rpm` is published today to the master-snapshot , I've triggered rebuild of ovirt-appliance. https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el8-x86_64/312/console
On Thu, Jul 16, 2020 at 4:31 PM Yedidyah Bar David <[email protected]> wrote: > On Thu, Jul 16, 2020 at 1:40 PM Yedidyah Bar David <[email protected]> > wrote: > > > > On Thu, Jul 16, 2020 at 1:14 PM Ehud Yonasi <[email protected]> wrote: > > > > > > 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. > > > > Thanks for the explanation. > > > > > > > > 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. > > > > But, if I got it right, the last "publish" run [1] started 5 hours > > after the check-merged [2] (one tells me 10 hours ago, other 15). Does > > it take time (e.g. waiting for resources) between finish of > > check-merged and copying to tested? We saw rather long queues lately > > (you already talked about this in other threads). > > > > Anyway, I'd not call it "urgent", but I'd rather make he-basic-master > > Green again before the weekend... (and this requires also building the > > appliance after you publish). > > I ran it myself, and it finished, saying successfully, but has an error - > and it didn't update wildfly (at least): > > > https://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/1801/consoleText > > 2020-07-16 11:44:54,374::INFO::repoman.common.stores.RPM::Adding > package > /srv/resources/repos/ovirt/tested/master/rpm/fc30/noarch/python2-ovirt-engine-lib-4.4.0-0.0.master.20200116192242.git2d9dd76235a.fc30.noarch.rpm > to repo Non persistent RPMStore > 2020-07-16 11:44:54,376::ERROR::repoman.cmd:: > 2020-07-16 11:44:54,376::ERROR::repoman.cmd::Error while adding > /srv/resources/repos/ovirt/tested/master/rpm:latest:only-missing > > Can you please check? Thanks. > > > > > Thanks, > > > > [1] > https://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/1800/ > > [2] > https://jenkins.ovirt.org/job/ovirt-engine-wildfly_standard-on-merge/33/ > > > > > > > > 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 <[email protected]> > 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 -- [email protected] > > >> To unsubscribe send an email to [email protected] > > >> 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/[email protected]/message/Q7QAW24L5AYRJVBFYWCTE7UW4DSFTSFN/ > > > > > > > > -- > > Didi > > > > -- > Didi > _______________________________________________ > Infra mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected]/message/4GIMHC3XTUGC3DIWI75RQXSUQBO3ANUB/ >
_______________________________________________ Infra mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/ZMMK4WJNMN6Q7HB54YFJ5ZIDIRWCC4GX/
