ivila commented on PR #211: URL: https://github.com/apache/incubator-teaclave-trustzone-sdk/pull/211#issuecomment-3076577222
> The `OPTEE-repo-build-and-run-examples-*-TAs` workflow tests the latest Teaclave TrustZone SDK commits against the [OP-TEE master branch from scratch](https://github.com/OP-TEE/manifest/blob/master/common.xml). The workflow consumes resources and facing network instability issues. > > However, I believe this approach is unnecessary. The Rust SDK should prioritize compatibility with **stable OP-TEE OS releases**, as testing and maintaining compatibility with the OP-TEE OS development branch should not be the primary focus of the Teaclave TrustZone SDK. > > Focusing on stable releases will significantly streamline the daily development workflow. For example: > > * A stable OP-TEE release triggers a QEMU image build. > * A QEMU image change prompts the republishing of the development Docker image, pinned to a specific OP-TEE version, supporting TA development and CI testing in both standard and no-std environments. > * Teaclave SDK development and CI rely on this stable development Docker image. > > This approach mitigates the instability of the current CI workflow by leveraging a consistent, version-pinned Docker image. As the core maintainer of the CI pipelines @ivila @DemesneGH, I'd like to hear your feedback on this and align our focus of maintenance. I rarely use Docker for TrustZone development, as I prefer to use my dev board for both compilation and testing. However, I agree we should remove the `OPTEE-repo-build-and-run-examples-*-TAs` jobs. It’s good to keep the Docker image available, but as a quick solution, perhaps we should either `remove these specific jobs` or `only trigger them when changes are merged into main`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
