qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Daniel P . Berrangé
Subject: Re: [PATCH] gitlab-ci: Test compilation on Windows with MSYS2
Date: Wed, 17 Nov 2021 14:44:51 +0000
User-agent: Mutt/2.0.7 (2021-05-04)

On Wed, Nov 17, 2021 at 01:52:57PM +0000, Alex Bennée wrote:
> 
> Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
> 
> > On 11/16/21 08:05, Marc-André Lureau wrote:
> >> Hi
> >> 
> >> On Mon, Nov 15, 2021 at 6:31 PM Philippe Mathieu-Daudé <f4bug@amsat.org
> >> <mailto:f4bug@amsat.org>> wrote:
> >> 
> >>     On 11/15/21 15:06, Thomas Huth wrote:
> >>     > Gitlab also provides runners with Windows, we can use them to
> >>     > test compilation with MSYS2, in both, 64-bit and 32-bit.
> >>     >
> >>     > 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.
> >> 
> >> 
> >> I wonder why gitlab does not offer the docker executor. On the
> >> freedesktop gitlab instance, they have windows docker executor, which
> >> speeds up the build time. Maybe we could also have our own Windows
> >> runner for qemu?
> >
> > We could, foss.org provides the QEMU project with x86 VMs resources
> > we are not using. What we miss is a sysadmin willing to setup &
> > maintain a such runner.
> 
> I think we might also have Azure credits from MS, but the same issues
> about admin and setup probably exist.

I've never explored this in any way, but IIUC, Azure should have
ability to run *windows* containers. If that's possible, then we
could avoid the admin burden of a VM and just use throwaway windows
containers as we do for Linux.

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]