Thank you for replying, Sean.
you can start the discussion the one think i will say is that its unlikely that many will have time to implement this for you so you and your team will have to take lead on doing the work to run the third party ci on your own hardware and make the results available puhlicly.
I understand that while meeting the all conditions is ultimately necessary, we should focus on preparing for and aligning our efforts with the community towards submitting a third-party CI [1] environment and the results. Is my understanding correct? If so, I'm committed to setting up the third-party CI and making the results publicly available. In addition, regarding the phrase "on your own hardware", can I use our internally available hardware for CI testing?
in your case since you want toe test a hardware feature that likely cannot be emulated?
if you already have an internal jenkins system with your own provisioning system you can use that instead to set up
Arm CCA environment can be emulated by QEMU[2]. Can this be leveraged for proceeding CI testing? For example, we could set up and run CI tests in an emulated environment before executing them on the actual hardware. Internally, we are planning to do this. Would it be valuable to share this environment and the results with the community? By doing this, we'd like to discuss how to provide CI in advance. [1] https://docs.openstack.org/infra/openstackci/third_party_ci.html [2] https://linaro.atlassian.net/wiki/spaces/QEMU/pages/29051027459/Building+an+... Regards, Ryo Taketani