search

confidential-containers / guest-components

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

ci: update occlum ci #592

Closed Xynnn007 closed 1 week ago

Xynnn007 commented 1 week ago

Now we are using a ACTIONS_RUNNER_HOOK_JOB_COMPLETED ability provided by github action. This allows us not to explicitly define a post-run script in yaml. The post actions are defined onside the runner itself.

See documents: https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/running-scripts-before-or-after-a-job#triggering-the-scripts

cc @mythi

Xynnn007 commented 1 week ago

btw @BbolroC this would be a choice for IBM SE runner. The concrete repo could be decided by $GITHUB_REPOSITORY env in the script.

BbolroC commented 1 week ago

btw @BbolroC this would be a choice for IBM SE runner. The concrete repo could be decided by $GITHUB_REPOSITORY env in the script.

True, I will spread out this info to the CI guys for kata/confidential containers to remove those unnecessary steps in the workflows. Thanks a lot!

Xynnn007 commented 1 week ago

After merging this PR, I propose to cut a release of v0.9.0 guest-components and trustee. Any thoughts? @fitzthum @arronwy @mythi