ci: Use cicd-actions setup-bazel-cache and unblock user namespace for linux-sandbox actions#151
Conversation
This centralizes bazel caching logic within S-CORE and moves it into a central place of perfection.
The code in cicd-actions is better tested and should be considered a single source of perfection
License Check Results🚀 The license check job ran with the Bazel command: bazel run //:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s GitHub Actions CI workflows to use the centralized eclipse-score/cicd-actions implementations for Bazel caching and for unblocking Linux user namespaces required by Bazel’s linux-sandbox, and removes the now-redundant in-repo composite action.
Changes:
- Replace
bazel-contrib/setup-bazel@0.19.0witheclipse-score/cicd-actions/setup-bazel-cachein relevant workflows. - Replace the local composite action for linux-sandbox user namespaces with
eclipse-score/cicd-actions/unblock-user-namespace-for-linux-sandbox. - Delete the repository’s
.github/actions/unblock_user_namespace_for_linux_sandboxcomposite action.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| .github/workflows/copilot-setup-steps.yml | Switch Copilot setup workflow to centralized Bazel cache + linux-sandbox unblock actions. |
| .github/workflows/build_and_test_host.yml | Switch host build/test workflow to centralized Bazel cache + linux-sandbox unblock actions. |
| .github/workflows/build_and_test_cross_compilation.yml | Switch cross-compilation workflow to centralized Bazel cache + linux-sandbox unblock actions. |
| .github/actions/unblock_user_namespace_for_linux_sandbox/action.yml | Remove local composite action now replaced by centralized cicd-action. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Is there a reason why only use it for the build workflows and not for the other workflows using bazel? Ah, never mind, those use the workflow template from cicd workflows. |
There is now a release of cicd-actions! Lets make use of that and simplify our code.
cicd-workflows are also being updated: eclipse-score/cicd-workflows#125
setup-bazel-cache
This centralizes bazel caching logic within S-CORE and moves it into a central place of perfection.
unblock linux user namespaces for linux-sandbox
The code in cicd-actions is better tested and should be considered a single source of perfection