public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: devel@edk2.groups.io, quic_llindhol@quicinc.com,
	Sami Mujawar <Sami.Mujawar@arm.com>,
	"discuss@edk2.groups.io" <discuss@edk2.groups.io>,
	"gaoliming@byosoft.com.cn" <gaoliming@byosoft.com.cn>,
	"ardb+tianocore@kernel.org" <ardb+tianocore@kernel.org>,
	"sean.brogan@microsoft.com" <sean.brogan@microsoft.com>
Cc: "'Kinney, Michael D'" <michael.d.kinney@intel.com>,
	'Andrew Fish' <afish@apple.com>, nd <nd@arm.com>
Subject: Re: [edk2-discuss] [edk2-devel] Soft Feature Freeze starts now for edk2-stable202311
Date: Wed, 22 Nov 2023 14:21:02 +0100	[thread overview]
Message-ID: <c45286bc-1f3c-4aae-a457-95a71d7530c3@linaro.org> (raw)
In-Reply-To: <3f2b7d3d-dfc8-40ba-9bcb-f1d6b35ca689@quicinc.com>

W dniu 22.11.2023 o 13:26, Leif Lindholm pisze:
> On 2023-11-22 11:11, Sami Mujawar wrote:

>> [SAMI] The proposal above looks good to me. This may be slightly 
>> off topic, but can we also enable edk2-platform upstream CI as 
>> well, please? This would be helpful to catch issues much earlier. 
>> [/SAMI]

> Yes, this is a problem we need to solve, but we don't have the time 
> or resources to set up an upstream CI. What we've been thinking of
> is to let maintainers set up their own CI infrastructure and then
> have that perform any target-specific tasks and report back to
> upstream CI. It's been a few months since I last discussed this with
> Mike, but I think we were looking at 
> https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners
> as a possible tool.
> 
> This is probably not something we would like to tie into the edk2 
> mergify workflow (it would add too much delay), but localised to 
> edk2-platforms.
> 
> Any help with implementing that would be most appreciated :)

I can write CI jobs which would run tests for QEMU platforms:

- virt/x86-64 (i440fx/q35)
- virt/aarch64
- sbsa-ref/aarch64

Sbsa-ref is something I am working on daily.

If Github Actions is all what's needed then it can be done using 
platform provided runners (no self-hosted needed).


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



  reply	other threads:[~2023-11-22 13:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07  0:59 [edk2-devel] Soft Feature Freeze starts now for edk2-stable202311 gaoliming via groups.io
2023-11-09 12:02 ` Marcin Juszkiewicz
2023-11-09 13:11   ` Leif Lindholm
2023-11-22 11:11     ` [edk2-discuss] " Sami Mujawar
2023-11-22 12:26       ` Leif Lindholm
2023-11-22 13:21         ` Marcin Juszkiewicz [this message]
2023-11-22 13:49           ` Leif Lindholm
2023-11-22 23:45             ` Pedro Falcato

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=c45286bc-1f3c-4aae-a457-95a71d7530c3@linaro.org \
    --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