ivila commented on PR #243:
URL:
https://github.com/apache/teaclave-trustzone-sdk/pull/243#issuecomment-3425108748
> Thanks for the clarification. However, there are too many CI jobs
currently, and I think we should clean them up and clarify the purpose of them.
>
> Current we have:
>
> For each push and merge into `main`:
>
> * **`license`**
> * **`systest`**
> * **`test-on-{arm64,amd64}-host`**: build and run the **latest** SDK
changes on a **fixed** OP-TEE version
> * **`test-{std,nostd}-build-on-dev-docker`**: ensure the latest SDK
changes don’t break the build inside the development Docker environment
>
> When merging into `main`
>
> * **`Test in OP-TEE Repo`**: build and run the **latest** SDK changes
against the **latest** OP-TEE repository
>
> > _to catch errors introduced by our own changes (anything that happens
after our commits)._
>
> For this goal, I think it should be tested on **every push**, and our
`test-on-{arm64,amd64}-host` job already covers that.
>
> As for **`Test in OP-TEE Repo`**, it makes sense to treat it as a
**periodic test** between our SDK and the OP-TEE project, ensuring the two
projects stay compatible.
>
> So I'd prefer remove the “merge into main” trigger and keep it as a
**daily scheduled job** instead.
Copy that, changes applied.
--
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]
