[ovirt-devel] Re: Travis builds
On středa 11. listopadu 2020 15:17:52 CET Michal Skrivanek wrote: > > On 11 Nov 2020, at 11:17, Nir Soffer wrote: > > > > On Wed, Nov 11, 2020 at 10:33 AM Vojtech Juranek wrote: > >> Hi, > >> recently, I noticed Travis builds waits in the queue for a very long > >> time. > >> Looking around I found out Travis probably reduced resources for OSS > >> projects. > >> > >> Also I found out all projects should migrate from travis-ci.org to > >> travis- > >> ci.com by end of December 2020 [1] (see Q. When will the migration from > >> travis-ci.org to travis-ci.com be completed?). Recently they announce new > >> pricing model [2] when OSS projects will get some initial credit and > >> after > >> that either has to pay or ask the support for another credit (see section > >> "Building on a public repositories only" in [2]). > >> > >> Maybe time to migrate away from travis-ci to something else, e.g. GH > >> Actions?> > > I would avoid github only dependency. Libvrt and qemu moved to gitlab > > recently, I think we should check this option instead. > > or our jenkins? > > we are getting rid of that awful mock environment, slowly, but it’s > progressing… is there still any reason to run a separate thing then? if the builds are comparably fast as on Travis, yes, this would the best option > >> Thoughts? > >> > >> Vojta > >> > >> [1] > >> https://docs.travis-ci.com/user/migrate/open-source-repository-migration > >> [2] > >> https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing_ > >> __ 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/PFRTNEBW3I > >> FCUGPI5R3VN3LEMV7DGD4Z/> > > ___ > > 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/JSPSQ2AZBKT > > BWUKFLVXJQSDIQ5D5UNX5/ 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/VLH7XRWFXNH7ZG5OXRH6A5VFBYFID656/
[ovirt-devel] Re: Travis builds
> On 11 Nov 2020, at 11:17, Nir Soffer wrote: > > On Wed, Nov 11, 2020 at 10:33 AM Vojtech Juranek wrote: >> >> Hi, >> recently, I noticed Travis builds waits in the queue for a very long time. >> Looking around I found out Travis probably reduced resources for OSS >> projects. >> >> Also I found out all projects should migrate from travis-ci.org to travis- >> ci.com by end of December 2020 [1] (see Q. When will the migration from >> travis-ci.org to travis-ci.com be completed?). Recently they announce new >> pricing model [2] when OSS projects will get some initial credit and after >> that either has to pay or ask the support for another credit (see section >> "Building on a public repositories only" in [2]). >> >> Maybe time to migrate away from travis-ci to something else, e.g. GH Actions? > > I would avoid github only dependency. Libvrt and qemu moved to gitlab > recently, > I think we should check this option instead. or our jenkins? we are getting rid of that awful mock environment, slowly, but it’s progressing… is there still any reason to run a separate thing then? > >> Thoughts? >> >> Vojta >> >> [1] https://docs.travis-ci.com/user/migrate/open-source-repository-migration >> [2] >> https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing___ >> 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/PFRTNEBW3IFCUGPI5R3VN3LEMV7DGD4Z/ > ___ > 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/JSPSQ2AZBKTBWUKFLVXJQSDIQ5D5UNX5/ ___ 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/2HFZ4O4CBSAFNLOV23WJXURZKIDQYHWJ/
[ovirt-devel] ovirt-engine has been tagged (ovirt-engine-4.4.4)
___ 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/JI7VO6M7V3CGWUTNBAFVQCCTURG4JISE/
[ovirt-devel] bz 1875386 openssl conf files point at qemu-ca-certificate: status
Hi all,
I now finished verifying my patches, currently pushed to github [1].
Verified clean engine-setup and engine-setup upgrade from current
master. Didn't verify adding hosts nor encrypted migration between
them, but I think it should work.
With the top patch there, also verified pki-enroll-pkcs12.sh, which
verifies also pki-enroll-request.sh, with both default and
--ca-file=qemu-ca.
Now:
Currently, that's 16 patches. The entire stack diff ('git diff' from
master) is 580 lines, whereas with the current split ('git log
'--format=%h %s' -u' from master) it's 1045 lines (~ twice), but
perhaps easier to follow, and shows my thought/refinement process,
although probably many comments you might have on earlier patches I
already addressed in later ones. I also do not think we must have all
16 patches add all the extra load on CI, so didn't yet push to gerrit.
So I wonder if just to squash them to a single one, or something in
between, both for review and for eventual merging. We definitely need
all of them merged at once, or if we want to prevent breakage and
still merge splitted, quite a lot more work (which I don't have time
for). Comments are welcome.
[1] https://github.com/didib/ovirt-engine/commits/qemu-ca-fixes
Best regards,
--
Didi
___
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/6ZTTZRMPGINGWUPEEBJWCKUKIMTBCBBW/
[ovirt-devel] Re: Travis builds
On Wed, Nov 11, 2020 at 10:33 AM Vojtech Juranek wrote: > > Hi, > recently, I noticed Travis builds waits in the queue for a very long time. > Looking around I found out Travis probably reduced resources for OSS projects. > > Also I found out all projects should migrate from travis-ci.org to travis- > ci.com by end of December 2020 [1] (see Q. When will the migration from > travis-ci.org to travis-ci.com be completed?). Recently they announce new > pricing model [2] when OSS projects will get some initial credit and after > that either has to pay or ask the support for another credit (see section > "Building on a public repositories only" in [2]). > > Maybe time to migrate away from travis-ci to something else, e.g. GH Actions? I would avoid github only dependency. Libvrt and qemu moved to gitlab recently, I think we should check this option instead. > Thoughts? > > Vojta > > [1] https://docs.travis-ci.com/user/migrate/open-source-repository-migration > [2] > https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing___ > 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/PFRTNEBW3IFCUGPI5R3VN3LEMV7DGD4Z/ ___ 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/JSPSQ2AZBKTBWUKFLVXJQSDIQ5D5UNX5/
[ovirt-devel] Travis builds
Hi, recently, I noticed Travis builds waits in the queue for a very long time. Looking around I found out Travis probably reduced resources for OSS projects. Also I found out all projects should migrate from travis-ci.org to travis- ci.com by end of December 2020 [1] (see Q. When will the migration from travis-ci.org to travis-ci.com be completed?). Recently they announce new pricing model [2] when OSS projects will get some initial credit and after that either has to pay or ask the support for another credit (see section "Building on a public repositories only" in [2]). Maybe time to migrate away from travis-ci to something else, e.g. GH Actions? Thoughts? Vojta [1] https://docs.travis-ci.com/user/migrate/open-source-repository-migration [2] https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing 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/PFRTNEBW3IFCUGPI5R3VN3LEMV7DGD4Z/
