From: "Laszlo Ersek" <lersek@redhat.com>
To: Sean Brogan <spbrogan@outlook.com>,
devel@edk2.groups.io, michael.d.kinney@intel.com,
Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>
Cc: Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>,
Rebecca Cran <rebecca@bsdio.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] running CI locally
Date: Wed, 19 Aug 2020 19:59:47 +0200 [thread overview]
Message-ID: <2d9572c6-7549-d0ae-3ec9-95158cfef484@redhat.com> (raw)
In-Reply-To: <BN8PR07MB69623B8914DD4541C5B8C125C85D0@BN8PR07MB6962.namprd07.prod.outlook.com>
On 08/19/20 18:22, Sean Brogan wrote:
> Laszlo/Mike,
>
> This is the joy of distributed repositories.
> Remember edk2 ci is actually using edk2-pytool-extensions and
> edk2-pytool-library. Documentation is in those projects.
>
> https://github.com/tianocore/edk2-pytool-extensions/tree/master/docs
> https://github.com/tianocore/edk2-pytool-library/tree/master/docs
>
> I won't say they are great and I hope someday relatively soon we can
> talk about an edk2 static site generator that can include docs from
> multiple repositories (much like https://microsoft.github.io/mu/) as I
> think documentation on edk2 is a weak spot.
>
> Regarding Mono and nuget. It is one of those things we wish was
> different as we have found it very inconsistent across different
> distributions of linux. But we do have docs here.
> https://github.com/tianocore/edk2-pytool-extensions/blob/master/docs/usability/using_linux.md
>
>
> And more specifically here:
> https://github.com/tianocore/edk2-pytool-extensions/blob/master/docs/usability/using_extdep.md#a-note-on-nuget-on-linux
>
>
>
> Finally getting to why you don't run the compile.
> Core CI (stuart_ci_build) is a plugin runner. Compile test is just one
> of those tests. OvmfPkg is a platform and thus didn't opt into core ci
> compile testing. In the table here i tried to document that OvmfPkg
> didn't compile using core ci and that a user should look at the readme.
> https://github.com/tianocore/edk2/blob/master/.pytool/Readme.md#basic-status
>
>
> So for OvmfPkg we enabled what we call platform ci (stuart_build). I
> think the write up here is pretty complete (although i see it has no
> mention of mono either).
> https://github.com/tianocore/edk2/tree/master/OvmfPkg/PlatformCI
>
> One final note. Yes the logging to console is by default very brief.
> This is by design as it is easier to quickly look and see what test
> failed and then use the log file (as mike mentioned) to find the root
> cause.
>
> Hope that helps and it is great to see people using it. Feedback is
> much appreciated.
The documentation looks *awesome*, and it's entirely my fault that I
couldn't find it. I apologize.
I'll report back with more results.
Thanks!
Laszlo
next prev parent reply other threads:[~2020-08-19 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 12:27 running CI locally Laszlo Ersek
2020-08-19 15:29 ` [edk2-devel] " Michael D Kinney
2020-08-19 16:22 ` Sean
2020-08-19 17:59 ` Laszlo Ersek [this message]
2020-08-21 7:23 ` Laszlo Ersek
2020-08-21 21:36 ` Sean
2020-08-24 12:35 ` Laszlo Ersek
[not found] ` <162D662A3371B4DC.7353@groups.io>
2020-08-21 21:50 ` Sean
2020-08-19 17:56 ` Laszlo Ersek
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=2d9572c6-7549-d0ae-3ec9-95158cfef484@redhat.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