qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Yonggang Luo" <luoyonggang@gmail.com>,
	"Marc-André Lureau" <marcandre.lureau@gmail.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	QEMU <qemu-devel@nongnu.org>
Subject: Re: [PATCH] gitlab-ci: Test compilation on Windows with MSYS2
Date: Wed, 17 Nov 2021 14:44:51 +0000	[thread overview]
Message-ID: <YZUVY/kzy7uH0KDn@redhat.com> (raw)
In-Reply-To: <874k8ax504.fsf@linaro.org>

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	other threads:[~2021-11-17 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 14:06 [PATCH] gitlab-ci: Test compilation on Windows with MSYS2 Thomas Huth
2021-11-15 14:29 ` Philippe Mathieu-Daudé
2021-11-16  7:05   ` Marc-André Lureau
2021-11-16  8:26     ` Philippe Mathieu-Daudé
2021-11-17 13:52       ` Alex Bennée
2021-11-17 14:44         ` Daniel P. Berrangé [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YZUVY/kzy7uH0KDn@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=luoyonggang@gmail.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).