Re: EDK2 CI and edk2-platforms
There are a few challenges with the model of the edk2-platforms repo given that it doesn't have tracking of edk2 or any other dependency (submodule or otherwise). It also has no clear owner or anyone driving repository wide initiatives (like ci).toggle quoted messageShow quoted text
Ignoring that, the work to enable a "core ci" and "platform ci" in edk2-platforms would depend on the complexity of the build process of your platform but should be pretty small.
First you need to support the pytools based build process (https://github.com/tianocore/edk2-pytool-extensions). After that it just requires using the existing azurepipeline template files.
As an example see what is needed to enable "platform ci" for OVMF is here (and this includes additional work for automatic execution on qemu).
To enable core CI
you need this per package: https://github.com/tianocore/edk2/blob/master/OvmfPkg/OvmfPkg.ci.yaml
And some sort of very simple https://github.com/tianocore/edk2/blob/master/.pytool/CISettings.py
Another example is
A third example you can compare to for a platform that resides outside the edk2 tree is our Project Mu platform repo here:
but this is based on the Project Mu version of edk2 code and uses submodules to track dependencies.
Anyway, it has been talked about off and on, for the last few years but in my opinion the platform owners need to enable this.
Here is one effort Jeremiah Cox did to enable a more complicated Intel KBL based minplatform using pytools. (step 1 of getting platform ci) https://github.com/out0xb2/edk2-platforms/tree/feature/openkbl/galagopro3 It was presented at a edk2 community meeting in 2019 but was never picked up by the platform owners.
On 1/7/2021 10:00 AM, Jeff Brasen wrote: