Re: [RFC PATCH] gitlab-ci: Test compilation on Windows with MSYS2

["Daniel P. Berrangé" <berrange@redhat.com>]

On Fri, Jul 09, 2021 at 09:52:18AM +0200, Thomas Huth wrote:
> Gitlab also provides runners with Windows, we can use them to
> test compilation with MSYS2.
> 
> However, it takes quite a long time to set up the VM, so to
> stay in the 1h time frame, we can only compile and check one
> target here. And there is also still a problem with compiling
> the multiboot.bin in pc-bios/optionrom/, so this is currently
> disabled, too.

THe gitlab VM provisioning seems quite fast (2+1/2 minutes),
so I guess you mean the time is sunk in intsalling msys
packages.

In the crurent Cirrus job there's a bunch of code that is
done to cache all the msys install, so that 90% of the time
we're merely extracting a local zipfile.

I wonder if we can do similar caching here. Perhaps even
have 2 seprate jobs running on the windows runner. The
first job can just build a zip file and store it as an
artifact and cache it in gitlab for speed. The second
job can do the actual build ?

> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  I'm sending this out as an RFC in case somebody else wants to play
>  with this. Considering that the corresponding job in Cirrus-CI compiles
>  way more targets within 1 hour, we might rather want to keep using
>  the Cirrus-CI job instead?

Yes, unless we can do the same kind of caching tricks to speed it
all up.

> 
>  .gitlab-ci.d/qemu-project.yml |  1 +
>  .gitlab-ci.d/windows.yml      | 59 +++++++++++++++++++++++++++++++++++
>  2 files changed, 60 insertions(+)
>  create mode 100644 .gitlab-ci.d/windows.yml

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