public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, ardb@kernel.org,
	mikuback@linux.microsoft.com,
	Michael Kinney <michael.d.kinney@intel.com>,
	Leif Lindholm <quic_llindhol@quicinc.com>
Subject: Re: [edk2-devel] Quick Change to Improve edk2 CI Time
Date: Sat, 27 Jul 2024 16:29:03 -0600	[thread overview]
Message-ID: <e9f28a6e-4433-4199-aa10-1320715386b9@bsdio.com> (raw)
In-Reply-To: <CAMj1kXE9BsR1OQQKrksSNPYqLiv=PYS_n-axJiP-__QHi5dajg@mail.gmail.com>

On 7/27/24 5:14 AM, Ard Biesheuvel wrote:

> Getting the CI delay down would help me a lot. But we also need a way
> for maintainers -who are ultimately in charge of their packages- to
> simply overrule the CI and merge a PR regardless of the CI outcome.
>
> Without this, I am seriously considering whether being a maintainer in
> Tianocore is worth the effort for me.

If it comes to it, I'd be willing to donate money to the project to 
allow us to purchase CI resources, or donate time on the machines I own, 
moving them into a datacenter if needed. Though I know in the past 
there's been a strong reluctance against using anything that isn't 
cloud-based.


-- 
Rebecca Cran



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120057): https://edk2.groups.io/g/devel/message/120057
Mute This Topic: https://groups.io/mt/107567922/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



      reply	other threads:[~2024-07-27 22:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26 20:03 [edk2-devel] Quick Change to Improve edk2 CI Time Michael Kubacki
2024-07-27 11:14 ` Ard Biesheuvel
2024-07-27 22:29   ` Rebecca Cran [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-list 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=e9f28a6e-4433-4199-aa10-1320715386b9@bsdio.com \
    --to=devel@edk2.groups.io \
    /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