From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Ben Dooks <qemu@ben.fluff.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: out of CI pipeline minutes again
Date: Thu, 23 Feb 2023 15:33:00 +0000 [thread overview]
Message-ID: <Y/eHLCKcdYk0V4Tt@redhat.com> (raw)
In-Reply-To: <20230223152836.dpn4z5fy6jg44wqi@hetzy.fluff.org>
On Thu, Feb 23, 2023 at 03:28:37PM +0000, Ben Dooks wrote:
> On Thu, Feb 23, 2023 at 12:56:56PM +0000, Peter Maydell wrote:
> > Hi; the project is out of gitlab CI pipeline minutes again.
> > In the absence of any other proposals, no more pull request
> > merges will happen til 1st March...
>
> Is there a way of sponsoring more minutes, could people provide
> runner resources to help?
IIUC, we already have available compute resources from a couple of
sources we could put into service. The main issue is someone to
actually configure them to act as runners *and* maintain their
operation indefinitely going forward. The sysadmin problem is
what made/makes gitlab's shared runners so incredibly appealing.
With 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 :|
next prev parent reply other threads:[~2023-02-23 15:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 12:56 out of CI pipeline minutes again Peter Maydell
2023-02-23 13:46 ` Thomas Huth
2023-02-23 14:14 ` Daniel P. Berrangé
2023-02-23 14:15 ` Warner Losh
2023-02-23 15:00 ` Daniel P. Berrangé
2023-02-23 15:28 ` Ben Dooks
2023-02-23 15:33 ` Daniel P. Berrangé [this message]
2023-02-23 22:11 ` Eldon Stegall
2023-02-24 9:16 ` Gerd Hoffmann
2023-02-24 14:07 ` Alex Bennée
2023-02-27 16:59 ` Daniel P. Berrangé
2023-02-27 17:43 ` Stefan Hajnoczi
2023-03-01 4:51 ` Eldon Stegall
2023-03-01 9:53 ` Alex Bennée
2023-03-21 16:40 ` Daniel P. Berrangé
2023-03-23 5:53 ` Eldon Stegall
2023-03-23 9:05 ` Alex Bennée
2023-03-23 9:18 ` Paolo Bonzini
2023-02-24 9:54 ` Paolo Bonzini
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=Y/eHLCKcdYk0V4Tt@redhat.com \
--to=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu@ben.fluff.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.