On Thu, Apr 29, 2021 at 10:33:46AM +0200, Philippe Mathieu-Daudé wrote: > Add a job which builds virtiofsd without any emulation or tool. > > Signed-off-by: Philippe Mathieu-Daudé <[email protected]> > --- > https://gitlab.com/philmd/qemu/-/jobs/1222007991 > Duration: 7 minutes 48 seconds > --- > .gitlab-ci.yml | 13 +++++++++++++ > 1 file changed, 13 insertions(+) > > diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml > index 52d65d6c04f..ba3c7ade6ca 100644 > --- a/.gitlab-ci.yml > +++ b/.gitlab-ci.yml > @@ -800,6 +800,19 @@ build-libvhost-user: > - meson > - ninja > > +build-virtiofsd-fedora: > + <<: *native_build_job_definition > + needs: > + job: amd64-fedora-container > + variables: > + IMAGE: fedora > + CONFIGURE_ARGS: --enable-virtiofsd > + --disable-system --disable-user --disable-tools --disable-docs > + artifacts: > + expire_in: 2 days > + paths: > + - build/tools/virtiofsd/virtiofsd
I'm not convinced that this job is justiable given our need to keep the total CI pipeline size constrained. The precedent this sets is that we need to test every configure args combination for each binary we build. That is not scalable as a pattern. Neither this virtiofsd arg scenario, nor others is going to be commonly used by downstream consumers of QEMU, so the payoff from having this job is also small. 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 :|
