On Wed, Nov 11, 2020 at 4:18 PM Michal Skrivanek <
michal.skrivanek(a)redhat.com> wrote:
> On 11 Nov 2020, at 11:17, Nir Soffer <nsoffer(a)redhat.com> wrote:
>
> On Wed, Nov 11, 2020 at 10:33 AM Vojtech Juranek <vjuranek(a)redhat.com>
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?
Current CI cannot run lot of tests, we have tons of skipped tests in
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 we get:
- new fresh vm for every test run
- simple CI configuration
- fast builds
It can work.
But I think in general depending on a single provider is bad, and it is
better
to have CI in multiple providers.