- Fix shell scripting issue with unquoted variables in forward-logs.sh
- Add error handling to hook script before executing forward-logs.sh
- Use null-terminated while loop to handle filenames with spaces
Add optional feature to forward GitHub Actions build logs to pod stdout
after job completion, enabling capture through Kubernetes logging solutions.
Changes:
- Add logForwarding.enabled config option (default: false)
- Create forward-logs.sh script to output worker logs with delimiters
- Integrate with job-completed hook system
- Update all Dockerfile variants to include script
- Modify Helm templates to pass FORWARD_BUILD_LOGS env var
- Support all container modes (default, dind, kubernetes, kubernetes-novolume)
Resolves#2478
* feat: allow to discover runner statuses
* fix manifests
* Bump runner version to 2.289.1 which includes the hooks support
* Add feedback from review
* Update reference to newRunnerPod
* Fix TestNewRunnerPodFromRunnerController and make hooks file names job specific
* Fix additional TestNewRunnerPod test
* Cover additional feedback from review
* fix rbac manager role
* Add permissions to service account for container mode if not provided
* Rename flag to runner.statusUpdateHook.enabled and fix needsServiceAccount
Co-authored-by: Yusuke Kuoka <ykuoka@gmail.com>
robert lestak
Yusuke Kuoka
Felipe Galindo Sanchez