* Packages Missing CI YAML Files
@ 2022-08-01 22:27 Michael Kubacki
2022-08-01 22:41 ` Ard Biesheuvel
0 siblings, 1 reply; 3+ messages in thread
From: Michael Kubacki @ 2022-08-01 22:27 UTC (permalink / raw)
To: 'Leif Lindholm', Ard Biesheuvel, abner.chang,
Daniel Schaefer, Chasel Chiu, Nate DeSimone, Star Zeng,
Jian J Wang, Hao A Wu, devel@edk2.groups.io
Hello Package Maintainers & Reviewers,
Is it intentional that these packages do not have a .ci.yaml file?
1. EmbeddedPkg
2. IntelFsp2Pkg
3. IntelFsp2WrapperPkg
4. SignedCapsulePkg
5. SourceLevelDebugPkg
This impacts CI running against these packages.
Regards,
Michael
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Packages Missing CI YAML Files
2022-08-01 22:27 Packages Missing CI YAML Files Michael Kubacki
@ 2022-08-01 22:41 ` Ard Biesheuvel
2022-08-02 1:21 ` [edk2-devel] " Michael Kubacki
0 siblings, 1 reply; 3+ messages in thread
From: Ard Biesheuvel @ 2022-08-01 22:41 UTC (permalink / raw)
To: Michael Kubacki
Cc: Leif Lindholm, abner.chang, Daniel Schaefer, Chasel Chiu,
Nate DeSimone, Star Zeng, Jian J Wang, Hao A Wu,
devel@edk2.groups.io
Hello Michael,
On Tue, 2 Aug 2022 at 00:28, Michael Kubacki
<mikuback@linux.microsoft.com> wrote:
>
> Hello Package Maintainers & Reviewers,
>
> Is it intentional that these packages do not have a .ci.yaml file?
>
> 1. EmbeddedPkg
> 2. IntelFsp2Pkg
> 3. IntelFsp2WrapperPkg
> 4. SignedCapsulePkg
> 5. SourceLevelDebugPkg
>
> This impacts CI running against these packages.
>
I'm not sure what you mean with 'intentional'. Originally, no packages
had .ci.yaml files, and over time, they were contributed for most of
the packages.
If anyone wants to contribute .ci.yaml files for these packages as
well, I would not object, so I guess it is not intentional in that
sense, as far as I am concerned. But if the policy today is that all
packages must have .ci.yaml files, I'm not sure who is on the hook to
realize that.
--
Ard.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [edk2-devel] Packages Missing CI YAML Files
2022-08-01 22:41 ` Ard Biesheuvel
@ 2022-08-02 1:21 ` Michael Kubacki
0 siblings, 0 replies; 3+ messages in thread
From: Michael Kubacki @ 2022-08-02 1:21 UTC (permalink / raw)
To: devel, ardb
Cc: Leif Lindholm, abner.chang, Daniel Schaefer, Chasel Chiu,
Nate DeSimone, Star Zeng, Jian J Wang, Hao A Wu
I meant are the maintainers aware that their package does not have a
.ci.yaml file and they have intentionally made the decision to not
include the file.
Different packages are in different states. Some package maintainers
have explicitly chosen to comment out various plugins, put others in
audit mode, etc. It could also be decided to not have the file at all.
I'm also not sure who is responsible for ensuring whether all packages
have the file.
On 8/1/2022 6:41 PM, Ard Biesheuvel wrote:
> Hello Michael,
>
> On Tue, 2 Aug 2022 at 00:28, Michael Kubacki
> <mikuback@linux.microsoft.com> wrote:
>>
>> Hello Package Maintainers & Reviewers,
>>
>> Is it intentional that these packages do not have a .ci.yaml file?
>>
>> 1. EmbeddedPkg
>> 2. IntelFsp2Pkg
>> 3. IntelFsp2WrapperPkg
>> 4. SignedCapsulePkg
>> 5. SourceLevelDebugPkg
>>
>> This impacts CI running against these packages.
>>
>
> I'm not sure what you mean with 'intentional'. Originally, no packages
> had .ci.yaml files, and over time, they were contributed for most of
> the packages.
>
> If anyone wants to contribute .ci.yaml files for these packages as
> well, I would not object, so I guess it is not intentional in that
> sense, as far as I am concerned. But if the policy today is that all
> packages must have .ci.yaml files, I'm not sure who is on the hook to
> realize that.
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-08-02 1:21 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-08-01 22:27 Packages Missing CI YAML Files Michael Kubacki
2022-08-01 22:41 ` Ard Biesheuvel
2022-08-02 1:21 ` [edk2-devel] " Michael Kubacki
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox