ci: update occlum ci #592
Merged
ci: update occlum ci #592
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 Signed-off-by: Xynnn007 <[email protected]>
|
btw @BbolroC this would be a choice for IBM SE runner. The concrete repo could be decided by |
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! |
mythi
approved these changes
Jun 20, 2024
arronwy
approved these changes
Jun 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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