confidential-containers / guest-components

Confidential Containers Guest Tools and Components
Apache License 2.0
71 stars 76 forks source link

ci: Fix occlum attester CI #581

Closed Xynnn007 closed 2 weeks ago

Xynnn007 commented 2 weeks ago

Now occlum ci does not work correctly. Because the runner does not run normally, s.t. https://github.com/confidential-containers/guest-components/actions/workflows/aa_occlum_sgx.yml. Some solutions

  1. delete this test as enclave-cc HW e2e test will cover this
  2. re-register the runner of ecc to org. Re-use the runner and fix the ci pipeline
Xynnn007 commented 2 weeks ago

cc @mythi

Xynnn007 commented 2 weeks ago

If we are with 2. We already have a runner under enclave-cc repo but that is not an organization runner. Luckily this runner is provided by alibaba and I can login, here is the plan

  1. Login to the VM and shutdown enclave-cc GH listener
  2. Delete the ecc runner from repo
  3. Add it as an organization runner
  4. Fix the ci yaml on both enclave-cc side and guest-components side

Before this, let me temporarily close the CI, as it marks self-hosted as runs-on, which will force all self-runners to run the test.