[libvirt PATCH 2/5] gitlab: reduce number of cross-build CI jobs

Daniel P. Berrangé berrange at redhat.com
Fri Mar 20 15:01:32 UTC 2020


On Fri, Mar 20, 2020 at 03:57:40PM +0100, Erik Skultety wrote:
> On Tue, Mar 10, 2020 at 10:09:42AM +0000, Daniel P. Berrangé wrote:
> > We're going to add more build jobs to CI, and users have limited time
> > granted on the shared CI runners. The number of cross-build jobs
> > currently present is not sustainable, so cut it down to two interesting
> > jobs to cover big endian and 32-bit platform variants.
> >
> > Signed-off-by: Daniel P. Berrangé <berrange at redhat.com>
> > ---
> >  .gitlab-ci.yml | 37 ++++++-------------------------------
> >  1 file changed, 6 insertions(+), 31 deletions(-)
> >
> > diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> > index 6f7e0ce135..b6a8db7881 100644
> > --- a/.gitlab-ci.yml
> > +++ b/.gitlab-ci.yml
> > @@ -5,29 +5,12 @@
> >      - ../autogen.sh $CONFIGURE_OPTS || (cat config.log && exit 1)
> >      - make -j $(getconf _NPROCESSORS_ONLN)
> >
> > -# We could run every arch on every versions, but it is a little
> > -# overkill. Instead we split jobs evenly across 9, 10 and sid
> > -# to achieve reasonable cross-coverage.
> > -
> > -debian-9-cross-armv6l:
> > -  <<: *job_definition
> > -  image: quay.io/libvirt/buildenv-libvirt-debian-9-cross-armv6l:latest
> > -
> > -debian-9-cross-mips64el:
> > -  <<: *job_definition
> > -  image: quay.io/libvirt/buildenv-libvirt-debian-9-cross-mips64el:latest
> > -
> > -debian-9-cross-mips:
> > -  <<: *job_definition
> > -  image: quay.io/libvirt/buildenv-libvirt-debian-9-cross-mips:latest
> > -
> > -debian-10-cross-aarch64:
> > -  <<: *job_definition
> > -  image: quay.io/libvirt/buildenv-libvirt-debian-10-cross-aarch64:latest
> > -
> > -debian-10-cross-ppc64le:
> > -  <<: *job_definition
> > -  image: quay.io/libvirt/buildenv-libvirt-debian-10-cross-ppc64le:latest
> > +# There are many possible cross-arch jobs we could do, but to preserve
> > +# limited CI resource time allocated to users, we cut it down to two
> > +# interesting variants. The default jobs are x86_64, which means 64-bit
> > +# and little endian. We thus pick armv7l as an interesting 32-bit
> > +# platform, and s390x as an interesting big endian platform. We split
> > +# between Debian 10 and sid to help detect problems on the horizon.
> 
> Will the sid actually be reliable? I've been trying to install sid into a VM
> with lcitool for quite a while and it was broken every time I tried. On the
> other hand, those container images are static, so we're going to run "older"
> container builds and not get the latest development stuff, but I guess that's
> fine for these purposes.

Yeah, right now we're insulated from any instability in sid. In future
I'd like to dynamically generated containers on demand as part of the
gitlab job, at which point instability will be critical, but we can
worry about it when we get there.

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 :|




More information about the libvir-list mailing list