You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting a discussion here to see if more individuals in the community have opinions on how best to integrate target-based testing into edk2 CI.
There is a current proposed patch on the mailing list and can be seen reviewing this in GitHub: #3651
Feedback:
Overall, I think we should try to enable this with a solution that aligns with the following ideas:
Works cross platform (Windows and Linux dev machines)
Works both in the cloud for CI as well as locally. This means that it should only minimally leverage azurepipelines for enablement. It should be handled with "stuart" and the paltformbuild.py infrastructure.
This is a platform feature and should scale to any platform not just those in the edk2 tree.
The platform should define which tests should be run and how those tests need to be compiled and run. (ie control library class mapping)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Starting a discussion here to see if more individuals in the community have opinions on how best to integrate target-based testing into edk2 CI.
There is a current proposed patch on the mailing list and can be seen reviewing this in GitHub: #3651
Feedback:
Overall, I think we should try to enable this with a solution that aligns with the following ideas:
Another example can be seen here: https://github.com/microsoft/mu_tiano_platforms/tree/main/Platforms/QemuQ35Pkg
In my opinion this solution scales better and aligns with the 4 ideas above.
Thoughts?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions