On Tuesday, 14 December 2021 09:44:44 CET Nir Soffer wrote: > On Tue, Dec 14, 2021 at 10:14 AM Milan Zamazal <mzama...@redhat.com> wrote: > > > > > > Nir Soffer <nsof...@redhat.com> writes: > > > > > > > > > I'm using github CI now, no issue seen in the last week. > > > > > > > > > > > > But we have now a wrose issue, build-artifacts job fail randomly in one > > > of > > > the targets. This means there is no way to use the automatic OST run. > > > > > > > > > > > > Should we disable all vdsm tests on gerrit, and enable only x64_64 el8 > > > build artifacts so we can at least get working OST? > > > > > > > > Since tests on gerrit are unusable, we should do it this way, good idea. > > > > > > > > Nevertheless manually testing patches by pushing them to GitHub is > > tiresome, > > > This is not that bad, I'm using this flow for a few years: > > while work needed: > hack... > push -f github # push to my github fork > check the build in github > > git review # push to gerrit for review
which is basically the same workflow which we used when we run test also in Travis IIRC, so actually no change here ... > > > we should move to GitHub completely ASAP. The only thing > > missing is OST, right? > > > Yes. I think what we need is a way to start OST build with a github > pull request url: > > CUSTOM_REPOS=https://github.com/oVirt/{project}/pull/{7} > > Or if it is easier, a way to upload zip files to jenkins for running OST. If Jenkins wipes the workspace before/after each build, that won't be probably the most easy way to go. Github actions deliver the rpm in zip file, so we basically need * download this zip file before build and unzip * create local repo from it (vdsm.repo with baseurl=file://$PATH_TO_UNZIP_DIR) * use this local repo instead of previous Jenkins build artifact job URL So we just need to implement this or am I missing something and there are some issues with this approach and it's more complicated? > Once we have something like this, we can move vdsm to github. > > Triggering OST builds automatically ("gating") is nice to have and > can be done later. > > Nir > _______________________________________________ > Devel mailing list -- devel@ovirt.org > To unsubscribe send an email to devel-le...@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/devel@ovirt.org/message/Y6CO6UJG6SD4P > IUTPWTMBDT7CC6DGDOH/
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@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/devel@ovirt.org/message/L4ZFAC4I7AOKHDGESONS5K5R5CLQCZAW/
