From: "Sean" <spbrogan@outlook.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: edk2-platforms, continuous integration, testing, and you
Date: Wed, 4 Jan 2023 13:38:21 -0800 [thread overview]
Message-ID: <BY3PR19MB4900C4EA9695DDF63DC7556EC8F59@BY3PR19MB4900.namprd19.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
There has been a long standing ask to/from the Edk2/UEFI community to
improve the code contribution process, quality, and consistency of the
edk2-platforms repository.
In the weekly Tianocore Tools & CI meeting this topic has come up and
was discussed at the last meeting (12/12) Tools & CI Meeting -
2022-12-12 - YouTube
<https://www.youtube.com/watch?v=RlHv5v6YvCM&list=PLzduEkFEN7nXFjWyGOldPBO-aX02zwZc3&index=1>
There are two asks.
1. If you own any feature package or platform in edk2-platforms please
get involved in the discussion. The CI system should reflect the tests
and features that are important to the contributors of the repository.
A CI system for Edk2-Platforms · Discussion #3721 · tianocore/edk2
(github.com) <https://github.com/tianocore/edk2/discussions/3721>
2. If you own a feature package help get your package passing "Core CI"
and look at enabling more testing (host based unit tests and/or on
device functional tests).
There is a branch here: spbrogan/edk2-platforms at enable_ci_v1
(github.com)
<https://github.com/spbrogan/edk2-platforms/tree/enable_ci_v1> where I
have started to enable Core CI (started with Ext4Pkg and
Usb3DebugFeaturePkg as examples).
Thanks
Sean
[-- Attachment #2: Type: text/html, Size: 1797 bytes --]
next reply other threads:[~2023-01-04 21:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 21:38 Sean [this message]
2023-01-04 23:57 ` [edk2-devel] edk2-platforms, continuous integration, testing, and you Pedro Falcato
2023-01-05 1:52 ` Sean
2023-01-05 23:32 ` Pedro Falcato
2023-01-05 23:48 ` Théo Jehl
2023-01-10 0:24 ` Isaac Oram
2023-01-13 22:32 ` Sean
2023-01-14 2:54 ` Pedro Falcato
2023-01-16 21:06 ` Michael D Kinney
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=BY3PR19MB4900C4EA9695DDF63DC7556EC8F59@BY3PR19MB4900.namprd19.prod.outlook.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