Re: [RFC PATCH] ci: ensure that all jobs use a shallow clone

[Daniel P . Berrangé]

On Thu, Jan 07, 2021 at 08:23:49PM +0100, Paolo Bonzini wrote:
> Il gio 7 gen 2021, 20:05 Thomas Huth <thuth@redhat.com> ha scritto:
> 
> > on travis-ci.com you can
> > only get free CI minutes for non-sponsored FOSS projects.
> > So let's simply not worry about Travis-CI anymore.
> >
> > Maybe we could rather disable shippable now that we support the cross
> > container builds on gitlab-ci, too?
> >
> 
> With pleasure, starting this discussion was an intended possible side
> effect of the patch. :)
> 
> The main issue with Travis is the non-x86 builders, which have no
> alternative yet.

The free travis accounts get 10000 credits. Linux jobs take 10 credits
per minute of execution time. Free credits are a one-off grant which
don't auto renew. You have to make an email request to travis to beg
for more each time they run out.

The non-x86 CI jobs we have in travis consume 91 minutes of time in
total.  So we'll burn through all free credits in 11 jobs and then
our CI will stop.

IOW, despite travis giving us non-x86 builders, it is doomed to be
unusuable, unless we can convince them to give us a *massively*
larger free credit allowance on the qemu account.  It would need to
be on the order x100 larger, and auto-renewing once a month to cope
with our rate of builds for the non-x86 CI jobs.

I think we need to just delete the travis config and accept that we
can't run those jobs unless we provide our own hardware for non-x86
in GitLab CI.  IIUC, the latter is something we're planning anyway.

So I support removing travis and shippable configs and focusing only
on GitLab and Cirrus

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|